Consider thread-local redirection of std::io handles
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 6.6k
- Forks
- 1.7k
- Avg merge
- 16h 14m
- Merged PRs (30d)
- 1
Description
Currently, stdout and friends in std::io are tied to the process-level handles, and are in turn used for println! and panic!. In the future, it could be useful to allow thread-local, or otherwise scoped redirection of these handles (especially one that would be inherited by child thread). In particular, that would allow a greater degree of composability between libraries.
See https://github.com/rust-lang/rfcs/pull/973 for one possible route.
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 by reading the linked RFC 973 and the issue’s description of process-level std::io handles, println!, panic!, and child-thread inheritance. A contribution would need a settled design for scoped or thread-local redirection before implementation work can be considered complete.
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
- 20/100