Add support for bulk spawn.

[lucteo]

We can spawn multiple computation in parallel, at the same time.

[kyouko-taiga]

The first question that popped in my mind while starting my review is: why do we need a special type to represent a collection of futures? Is there a way we could use Array or Buffer?

[lucteo]

The first question that popped in my mind while starting my review is: why do we need a special type to represent a collection of futures? Is there a way we could use Array or Buffer?

We can, but that would be inefficient. We would essentially be needing escaping futures, and thus we have one memory allocation for each computation. Using bulk_spawn we only need one memory allocation for the entire frame.

[kyouko-taiga]

Suggested change

	public type BulkFuture<E: Movable & Deinitializable> {
	public type FutureSet<E: Movable & Deinitializable> {

or

Suggested change

	public type BulkFuture<E: Movable & Deinitializable> {
	public type FutureArray<E: Movable & Deinitializable> {

?

The term "bulk" does not work for me. Even if we can't actually use Set, Array, or Buffer, at least we can probably relate this abstraction to one of these collection using its name.

[lucteo]

This is not an array of futures or a set of futures, but I see why you don't like it. It a future that waits on multiple actions to complete.

I'm thinking at this entire thing as supporting "bulk spawn"; initially, I had the name bulk_spawn_, and only later renamed it to spawn_. This is why the future still has "bulk" in it.

I would need to think some more about better naming.

[lucteo]

Renamed to FutureSet.

[kyouko-taiga]

Suggested change

	/// Initializes `self` with `f`, and spawns the computation.
	/// Initializes `self` with `action`, and spawns the computation.

I typically try to describe how a callback is called in the docs. We should know what index is and what values we can expect receiving in the lambda that we pass.

[lucteo]

Fixed.

[kyouko-taiga]

I'm a little surprised that this doesn't return anything. Is it because of current compiler limitations?

I would have expected to get a set/array/buffer out of the await call.

[lucteo]

I guess we can return something like an array. Bur, I would like to avoid another allocation and I would wish these elements to reside in the frame. Thus, we need to return a Collection type (random access) that is able to query the frame for the results.

But I would add this later, when we add more meat on the standard library.

[codecov]

Welcome to Codecov 🎉

Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.

Thanks for integrating Codecov - We've got you covered ☂️