Hacking rustc: Contributing to the Compiler
summary
Claim: anyone with Rust and time can modify rustc and get changes merged. Concrete steps: clone the repo, run x.py to build and test, use rustc dev guide and issue labels like emender and easy to find tasks. Reality check: full builds need lots of RAM and several dozen gigabytes of disk and the feedback loop commonly takes longer than 15 minutes. Debugging relies on debug symbols, printed logs and RUST_LOG style verbosity.
AI-written summary · about
chapters (9)
- 0:00Introduction to contributing
- 1:02Finding a task
- 3:28Working with labels
- 5:46Setting up the environment
- 7:02Tooling and workflow
- 8:10Internal resources
- 9:08Understanding the pipeline
- 10:32Compiler passes explained
- 13:18Conclusion and invitation
related talks
15mContributing to the Rust compiler with little to no code
29mRust is easy
32mrustc in userland
45mWhat it's Like to Work on Open Source
09mRustc: How I Learned to Respect the Compiler
25m"Compiler-Driven Development: Making Rust Work for You"
32mBuilding and Maintaining Rust at Scale
26mPiecing together Rust: It is more than just writing code