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

Store ~Task in thread local storage instead of ~Scheduler #6855

Closed
brson opened this issue May 31, 2013 · 2 comments
Closed

Store ~Task in thread local storage instead of ~Scheduler #6855

brson opened this issue May 31, 2013 · 2 comments
Labels
A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows

Comments

@brson
Copy link
Contributor

brson commented May 31, 2013

The current design places a ~Scheduler in TLS. This turned out to be a bad idea because now I want to have tasks that don't use a scheduler. Instead we should place ~Task in TLS. Once we do that we'll need a place to store the ~Scheduler instance when running in scheduler context, so we'll have to use a ~Task, making the scheduler itself a non-green thread task.

@metajack
Copy link
Contributor

Visiting for triage. Since this is internal, not nominating for a milestone.

@toddaaro
Copy link
Contributor

toddaaro commented Aug 6, 2013

Done.

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

3 participants