Tracking Issue for `alloc::io` and `core::io`
Open
Nobody has claimed this yet.
C-tracking-issue
S-tracking-unimplemented
T-libs
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
Feature gate: #![feature(alloc_io)]
This is a tracking issue for using module io in alloc (and hopefully in core one day).
Public API
alloc::io and core::io modules.
Steps / History
(Remember to update the S-tracking-* label when checking boxes.)
- ACP (accepted): https://github.com/rust-lang/libs-team/issues/755
- Implementation:
- Final comment period (FCP)^1
- Stabilization PR
Unresolved Questions
- None yet.
Contributor guide
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 implementation PRs (#155849, #154654, #155574, #155625, and #154684) and the alloc::io and core::io API scope in this issue. Done means completing the implementation checklist, resolving any open questions, then progressing through final comment period and a stabilization PR.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100