Compiler
Rust’s compiler team are responsible for maintaining the Rust compiler, improving its performance and considering the stabilization of compiler features.
We use the Forge to document the team’s processes, policies and working practices, if you’d like to read about how the compiler works and instructions on how to set up a development environment, you’re looking for the rustc-dev-guide.
- Backports
- How do I request a beta and/or stable backport of a compiler change? How will compiler backport nominations be handled?
- Calendar
- How do I subscribe to the compiler team’s calendar?
- Cross-team Collaboration
- How do I request the help of the compiler team?
- Meetings
- What meetings do the compiler team run and how can I attend?
- Membership
- What is expected of compiler team members and how do I join?
- Proposals, Approval and Stabilization
- How do I propose a change to the compiler team? What approval is necessary for my change?
- Repositories we maintain
- Various code repositories maintained by the Compiler Team
- Resources
- What useful resources are available for contributors and team members?
- Review Policy
- How do I make a contribution which is easy to review? How do I start reviewing as a team member?
- Supplemental Tools
- When can I shell out to tools like
stripinrustc? How should I triage issues with external tools?
- When can I shell out to tools like
- Third-party and Out-of-tree Crates Policy
- When can I add third-party crates to the compiler? When can I create a out-of-tree crate for the compiler?
- Triage and Prioritization
- How are compiler issues triaged and prioritized?
- Operations
- Supporting the compiler team
- Working Areas
- Specific areas of work around the compiler