Should we have a Rust 2021 edition?
summary
Argument: Rust’s edition mechanism proves it can opt into breaking changes safely — the async keyword reserved example and non-lexical lifetimes show concrete compiler work across AST→HIR→MIR→LLVMIR. Rust 2018 ships December 2018 but the schedule slips and contributor burnout are real; async await lands later. Proposal: a smaller, deliberate edition every three years with a three-year release train and an RFC timeline (plan by October 2020) so features, tooling and ecosystem upgrades happen predictably. oxide computer company and tooling like rustfix factor into rollout.
AI-written summary · about
chapters (26)
- 0:00Start
- 4:12Why Additions Matter
- 5:22Development of Rust
- 6:57Additions Are Not Allowed To Change Everything about Rust
- 8:06The Async Keyword
- 12:57New Keywords
- 13:10Repurpose Existing Syntax
- 14:20Module System
- 14:47Coherence Rule
- 16:09Changes to the Standard Library
- 19:05Multi-Pass Compiler
- 20:09Multi-Pass Compilers
- 21:19Semantic Analysis
- 21:56Code Generation
- 28:28Method Lookup
- 33:56Working with Rust and Fuchsia
- 34:44Compiler Architecture
- 36:03Incremental Compilation
- 41:20Russ 2018
- 44:40Preview Period
- 52:31Does Mozilla Hire Engineers To Work on Rusty and that Should Help Diminish Burnout
- 53:34Release Trains
- 55:46What Feature Should Be in Rest 2021
- 57:05Why a Three-Year Cadence
- 58:47Roadmap for the Year
- 1:03:40Function Overloading
