Talk:Rust compiler

Rust language vs rustc boundary

Because rustc is the reference compiler, language and compiler topics naturally overlap. To avoid scope drift:

• keep language-wide design philosophy in Rust (programming language);
• keep rustc-specific implementation details here (HIR/MIR pipeline, borrow-check pass location, diagnostics format, command-line flags, backend integration);
• mention a language feature only when tied directly to compiler implementation or compiler-facing workflow (for example editions via --edition and cargo fix --edition).

If a paragraph can apply equally to any hypothetical Rust compiler, consider moving or trimming it.

Naming and title

Current title is Rust compiler. This is the clearest reader-facing name and matches common usage in documentation ("the Rust compiler", "rustc").

Useful redirects:

• rustc
• Rustc
• Rust compiler (rustc)
• Rust compiler implementation

Technical content conventions

To keep the page stable and policy-compliant:

• Prefer short, version-resilient examples over full outputs that may drift between releases.
• For command examples, keep at least one minimal direct rustc invocation and one Cargo-driven workflow.
• Distinguish clearly between stable flags and nightly-only -Z flags.
• Avoid implying that experimental backends are production-default paths.
• Keep release/version numbers updated only when supported by a citation.

Outstanding tasks for editors

1. Strengthen independent sourcing for history. Add third-party sources for early development timeline, Mozilla transition period and Rust Foundation governance changes.
2. Add reception coverage. Include reliable independent commentary on diagnostics quality, compile-time trade-offs and compiler ergonomics.
3. Keep editions section compiler-focused. Ensure each edition bullet explains what rustc changes in behaviour for opted-in crates.
4. Watch backend status claims. Cranelift and gcc backend status can change quickly; qualify statements with dates and sources.
5. Check command-line examples per release. Verify that listed flags and sample invocations remain valid on current stable toolchains.