Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Task::spawn_many and Task::try_spawn_many #32

Open
austinjones opened this issue Aug 27, 2020 · 1 comment
Open

Add Task::spawn_many and Task::try_spawn_many #32

austinjones opened this issue Aug 27, 2020 · 1 comment
Labels
enhancement New feature or request

Comments

@austinjones
Copy link
Owner

austinjones commented Aug 27, 2020

If one of the inputs to Task::spawn was &Bus, lifeline could create and execute a group of message receivers, not just one.

Lifeline would take the bus, and a FnMut spawn function which receives &Bus and returns a Future. That would pull channels off the bus using rx::()?.

spawn_many would take a core size, and a max size. If the core size could not be fulfilled, the spawn would fail.

@austinjones austinjones added the enhancement New feature or request label Aug 27, 2020
@austinjones austinjones added this to the 0.4.0 milestone Sep 7, 2020
@austinjones
Copy link
Owner Author

This is interesting. Multiple tasks will need to share a lifeline value.

@austinjones austinjones modified the milestones: 0.4.0, 0.5.0 Oct 24, 2020
@austinjones austinjones removed this from the 0.5.0 milestone Jan 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant