Rust All-Hands 2026: 166 Rustaceans, 73 sessions, zero decisions—that’s the goal

Rust All-Hands 2026 (Utrecht, May) brought together 166 contributors across 73 sessions over 3 days. No formal decisions were made—this is the rule. However, several technical breakthroughs emerged: `rustc_public`, `cargo-semver-checks`, union semantics, and the allocator trait.

In plain terms. The Rust All-Hands 2026 retrospective, published on July 31, 2026, on the inside-rust blog, documents three days in Utrecht: 166 contributors, 73 sessions, 11 rooms. No formal decisions—final votes were explicitly excluded—but several technical breakthroughs.

The fact

Three-format structure: team sessions, unconference (60 ecosystem members—Bevy Engine, Ariel OS, Linebender, Safety-Critical Rust Consortium, Rust GPU, Rust Embedded), and governance discussions (Leadership Council, Project Directors).

Key technical advances:

• rustc_public unblocked in collaboration with the infrastructure team.
• cargo-semver-checks: consensus on the cross-crate analysis path.
• Operational semantics of unions finalized (FCPs in progress).
• Allocator Trait: renewed momentum toward stabilization.
• Discussions: const generics and const traits, field projections, Rust/C++ interoperability (Crubit, LLVM IR + Rust MIR), Rust for Linux, Rust for CPython, SIMD, custom lints, RFC process (TC39-inspired considered).

Our take

The format is an architectural choice. For a language adopting TC39-inspired RFC processes, the unconference acts as a bottleneck reliever—decisions remain asynchronous on GitHub, while in-person meetings unblock technical deadlocks. Next edition: Utrecht, May 27–29, 2027, as part of RustWeek.

To watch

Concrete follow-ups on open FCPs for unions; possible announcement on rustc_public; RustWeek 2027 agenda; effective adoption of cargo-semver-checks by major crates.