Repository navigation
Give schedulers and tasks useful names #2891
Description
Activity
Not critical for 0.6, de-milestoning
Nominating for milestone 5 (production-ready)
just a bug, removing milestone/nomination.
This should not be too hard, and would be super useful for writing test cases. All that's needed is an extra field in
TaskOpts, and anOption<~str>inside the Task struct. One place to print the name would be when the task fails or is killed; can't think of any others at the moment.does our notion of having multiple schedulers support naming them? it's not as obvious how to do that as it is how to name tasks.
I did this for tasks but not schedulers. Unassigning myself.
This is done now. I don't believe that we're going to want to give names to schedulers any time soon. That's an inherently M:N concept so libstd shouldn't be exposing that, and that's the use case that this is optimizing for anyway (naming tasks).
You can name a pthread on most operating systems. There are usually small length limits though.
- added a commit that references this issue
on May 12, 2023 - added a commit that references this issue
on Jun 4, 2026
tasks especially would be very helpful if they could be uniquely identified