Rust Zürisee Live Stream 2024-01-17

Rust

Contribute to improving the Rust compiler's diaystics, test, and review processes with the Rust team.

Key takeaways

Rust compiler has over 2000 issues, labeled as a-diagnostics, which need improvement.
Contributing to Rust compiler can be done by labeling issues as eNeedsTest.
Minimization is a satisfying process, but it’s also repetitive and can be automated using tools.
Rust compiler has a lint, but it’s not always easy to guess which issues need review.
Reviewing code takes time, and reviewers may not always respond in a timely manner.
Contributing to Rust compiler requires knowledge of compiler internals, but new contributors can start by reviewing existing issues.
Rust compiler has a separate compromise for review bandwidth, making it difficult for some teams to handle reviews.
Open-review process allows anyone to review code, but requires knowledge of compiler internals.
Rust compiler has a community-driven approach, with many contributors working together to improve the compiler.
There are many opportunities for contributors, including code reviews, issue triaging, and feature proposals.
Stabilizing a feature takes a long time, with a lot of discussion and testing required.
Contributing to Rust compiler can be a significant undertaking, requiring a good understanding of compiler internals and Rust programming language.
Tools like Clippy, RustAnalyser, Cargo, and RustFormat can be used to improve code quality and make it easier to contribute to the compiler.

More talks