A home for compiler team planning documents, meeting minutes, and other such things. If you're interested in learning about how rustc works -- as well as advice on building the compiler, preparing a PR, and other similar topics -- check out the rustc-guide.
- Where to find us: We are primarily present on Zulip, though some of us also monitor Discord.
- Want to attend a meeting or follow along? See the "meeting calendar" section below.
- Looking for technical information about how the compiler works? Check out the rustc-guide.
Our meeting calendar is publicly available from the following links:
- Web Link -- use this to view the calendar or to import into Google Calendar
- ICS file, for use outside from google calendar -- use this if you want to import into different calendar software
Unless otherwise noted, all our meetings are open to the public and held on Zulip. There are two main team-wide meetings that we hold on a regular basis. There are also a variety of working group meetings.
We have a weekly triage meeting to discuss and track regressions and urgent changes. This meeting is held on Zulip and open to anyone.
We also have a regular steering meeting where we discuss proposed designs, changes to our process, and other topics. The topics are scheduled at a planning meeting that occurs every four weeks.
- Have an idea? Click here to propose a topic to be scheduled by filing an issue with the correct template.
- Next planning meeting: June 7
- Scheduled meetings:
- June 14: Discuss the gcx, tcx transition, compiler-team#104
- June 28: Maintenance and triage, compiler-team#90
Much of the ongoing work and initiatives from the compiler team are performed by working groups. Working groups are a great way for new contributors to get involved as they provide a stream of tasks all focused around one area and have designated channels for help and advice. All of the active working groups are listed below:
| Name | Status | Short Description | Zulip Stream |
|---|---|---|---|
| Async-await Implementation | Active | Implementing async-await | #t-compiler/wg-async-await |
| LLVM | Incubating | Working with LLVM upstream to represent Rust in its development | #t-compiler/wg-llvm |
| Self-Profile | Active | Improving the -Z self-profile feature |
#t-compiler/wg-self-profile |
| RFC 2229 | Active | Make a closure capture individual fields of the variable rather than the entire composite variable | #t-compiler/wg-rfc-2229 |
| RLS 2.0 | Active | Experimenting with a new compiler architecture tailored for IDEs | #t-compiler/wg-rls2.0 |
| Meta | Active | How compiler team organizes itself | #t-compiler/wg-meta |
| Non-Lexical Lifetimes (NLL) | Winding down | Implementing non-lexical lifetimes | #t-compiler/wg-nll |
| Traits | Active | Improving the trait-system design + implementation | #t-compiler/wg-traits |
| Parallel-rustc | Active | Making parallel compilation the default for rustc | #t-compiler/wg-parallel-rustc |
| Profile-Guided Optimization | Active | Implementing profile-guided optimization for rustc | #t-compiler/wg-profile-guided-optimization |
| MIR Optimizations | Active | Write MIR optimizations and refactor the MIR to be more optimizable. | #t-compiler/wg-mir-opt |
| Rustc pipelining | Active | Enable Cargo to invoke rustc in a pipelined fashion, speeding up crate graph compiles. | #t-compiler/wg-pipelining |
| Polonius | Active | Exploring the integration of the "NLL 2.0"-like "Polonius analysis" into rustc | #t-compiler/wg-polonius |
| Learning | Active | Make the compiler easier to learn by ensuring that rustc-guide and api docs are "complete" | #t-compiler/wg-learning |
| Diagnostics | Active | Use crates.io crates for diagnostics rendering and make emitting diagnostics nicer. | #t-compiler/wg-diagnostics |
If you're interested in figuring out who can answer questions about a particular part of the compiler, or you'd just like to know who works on what, check out our experts directory. It contains a listing of the various parts of the compiler and a list of people who are experts on each one.
The procedures directory contains descriptions of various rustc procedures.
All interactions on this repository (whether on issues, PRs, or elsewhere) are governed by the Rust Code of Conduct.
Further, all content on this repository is subject to the standard Rust licensing.