Rust 1.100: Never Type Stable After a Decade, Allocator API, Cargo Guard Rust 1.100.0 shipped on November 12, stabilizing the never type `!` in every type position after ten years and five failed stabilization attempts, unblocked by the 2024 edition's change of type-inference fallback from `()` to `!`. The release also stabilizes the Allocator API constructors `Vec::new_in`, `Vec::with_capacity_in`, `Box::new_in` and `Box::from_raw_in`, adds a `DropGuard` helper, and introduces Cargo's `global-min-publish-age` resolver setting to block recently published crates. It is the 100th stable release since Rust 1.0 in May 2015, and `Infallible` is now a type alias for `!`, allowing `Result` directly. Rust 1.100.0 shipped on November 12. The headline is the never type — written as — which is now stable in every type position after ten years, five failed stabilization attempts, and an edition-level migration. That alone makes this a landmark release, but 1.100 also delivers a stable Allocator API for Vec and Box , a new DropGuard helper, and Cargo’s global-min-publish-age supply chain defense. It is one of the most feature-dense stable releases Rust has shipped, and the version number carries weight — this is the 100th stable release since Rust 1.0 in May 2015. The Never Type: Ten Years in the Making The never type, , represents computations that never produce a value — think functions that always panic, infinite loops, or early returns that diverge. It has existed in Rust’s nightly compiler for years. What took so long to stabilize it? The core problem was type inference fallback. When Rust cannot infer a concrete type, it falls back to a default. Prior to the 2024 edition, that fallback was the unit type . Switching the fallback to broke real crates — not theoretical ones, actual published packages — and every previous attempt had to be reverted. The 2024 edition finally changed the fallback to , which unblocked the stabilization PR merged in August 2026. What changes in practice? The Infallible type — the workaround developers have used for years to express “this error can never happen” — is now a type alias for . You can write Result