Skip to content

New tasks should always spawn into the default (general) scheduler unless otherwise requested #3760

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

Closed
brson opened this issue Oct 14, 2012 · 1 comment
Labels
A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows

Comments

@brson
Copy link
Contributor

brson commented Oct 14, 2012

The most common reason for creating a new scheduler is because you are going to block and need to get out of the way of other tasks. It's very easy to accidentally spawn more tasks onto your single threaded scheduler then block them.

This will require making schedulers first class so that those that actually want to spawn onto a specific scheduler can, and also a scheme for keeping track of the default scheduler (and keeping it alive). May require new atomic reference counting.

@brson
Copy link
Contributor Author

brson commented Jan 29, 2013

Fixed.

@brson brson closed this as completed Feb 6, 2013
bors pushed a commit to rust-lang-ci/rust that referenced this issue May 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows
Projects
None yet
Development

No branches or pull requests

1 participant