More robust treatment of uncaught panics for child threads
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 6.6k
- Forks
- 1.7k
- Avg merge
- 16h 14m
- Merged PRs (30d)
- 1
Description
Currently, an uncaught panic on a child thread will result in output to that thread's panic output handle (which is currently overridable).
This may not be a desirable default, and we probably want the behavior to be more thoroughly customizable.
See this previous RFC for some discussion on the topic.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the issue description and read the linked previous RFC 519 for the existing discussion about child-thread panic handling. Since no source files, tests, or concrete behavior are identified, first clarify the desired default and customization model; done would require an agreed, actionable RFC scope rather than an implementation inferred from this issue alone.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100