rust-lang / rust-lang/rustc-dev-guide
Tracking issue for "Compiler walkthrough" section
Open
Nobody has claimed this yet.
C-tracking-issue
E-hard
T-compiler
X-workthrough
- Dominant language
- HTML
- Stars
- 1.9k
- Forks
- 613
- Avg merge
- 17h 24m
- Merged PRs (30d)
- 39
Description
(name is to-be-bikeshedded)
- Implement integer32llc/rust-playground#502 [@jyn514]
- Implement
-Z unpretty={ast-tree,thir-tree}[@LeSeulArtichaut]- AST: rust-lang/rust#82304
- THIR: rust-lang/rust#82860
- Implement (an MVP of)
-Z dump-internal-data[@camelid]
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 remaining checklist items: integer32llc/rust-playground#502 and the proposed MVP of -Z dump-internal-data; review the linked AST, HIR, THIR, and rustc issues or pull requests for context. Done means the compiler walkthrough section is implemented and all applicable checklist items are completed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100