rust-lang / rust-lang/rustc-dev-guide
Fill in holes in backend chapters
Open
Nobody has claimed this yet.
A-cg-cranelift
A-codegen
A-const-eval
A-LLVM
A-monomorphization
C-enhancement
C-tracking-issue
E-hard
T-compiler
- Dominant language
- HTML
- Stars
- 1.9k
- Forks
- 613
- Avg merge
- 17h 24m
- Merged PRs (30d)
- 39
Description
We are collecting holes issues in this doc so we can incrementally improve them: https://hackmd.io/fTJHEkb5TXuKh2ClBL_c_w
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 reviewing the linked HackMD document to identify which backend-chapter holes are in scope. Confirm the relevant rustc-dev-guide chapter locations before making changes; done means the selected missing material is filled in and the guide no longer has those documented gaps.
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