rust-lang / rust-lang/std-dev-guide
Add a standard library stabilization "things to double-check" list
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 90
- Forks
- 47
- Avg merge
- 9h 22m
- Merged PRs (30d)
- 1
Description
The "if it's a new trait it needs to have &mut blankets immediately" problem came up on IRLO recently: https://internals.rust-lang.org/t/implement-std-asrawfd-for-references/20132/5?u=scottmcm
We've been better about this for newer traits, but it reminded me that it would be good to have a list of "stuff we can't fix later" to double-check for every FCP, which would also be a good resource for people making ACPs to think about.
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 linked IRLO discussion about implementing std traits for references, then review how this guide currently describes FCPs and ACPs. Define the “things we can’t fix later” checks and add a reusable stabilization checklist for those processes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100