Rust 1.100.0: The Never Type Finally Lands After a Decade and Five Attempts

Rust 1.100.0 was released on November 12, 2026, and its headline is a feature that has been in progress for a decade: the never type, written as !, is now stable. The language attempted to stabilize it five times over ten years; this time it shipped.

What the never type does

The never type represents computations that never complete — functions that always panic, loop forever, or exit the process. Before 1.100.0, the ! type existed internally in the compiler but could not be used directly in code. You could write a function that returned it in practice, but you could not name it, store it, or use it cleanly as a generic parameter.

As of 1.100.0, ! can be written anywhere a type is expected. The enum Infallible — the standard workaround for "this error can never happen" — is now a type alias for !. The compiler's fallback when it cannot infer an integer type has also changed: it used to default to (); it now defaults to !.

That fallback change is the one breaking change to watch. Phoronix notes that code written before the 2024 Rust edition that relied on the old behavior may need minor updates. The release notes recommend testing against the beta toolchain before upgrading production builds.

Custom allocators finally land

The release also stabilizes the core of the long-awaited Allocator API: the Allocator trait, the Global and System allocators, and Box::allocator and Vec::allocator. This lets library authors write data structures that work with custom memory allocators without reaching for unsafe code or external crates.

Initially, only Box and Vec can accept a custom allocator parameter. The plan is to extend this to other collections and pointer types in future releases.

Cargo gains supply chain tools

The cargo side of the release ships two features aimed at dependency hygiene. Unused dependency warnings will now surface in cargo check output by default, flagging dependencies that could be removed without breaking the build. And a new min-publish-age setting lets crate authors require a minimum time between a dependency's initial publication and when it can be used in a release — a lightweight countermeasure against supply chain attacks that swap in a malicious crate before the community notices.

Rust 1.100.0 is a release that closes a lot of open loops. The never type alone has been attempted five times since work began around 2015. Having it stable, alongside the Allocator API and Cargo's supply chain tools, makes this one of the more substantive releases in recent memory.