New tasks should always spawn into the default (general) scheduler unless otherwise requested #3760
Labels
A-runtime
Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows
Milestone
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.
The text was updated successfully, but these errors were encountered: