1min.

1MIN · RUST

Rust 1.100 stabilizes the never type beyond function returns

Rust 1.100 lets developers name the never type, written !, anywhere a type is accepted. It represents computations that cannot produce a value, so Result<T, !> can express an operation with no possible error value. The release also changes never-type fallback in older editions, which can expose rare compatibility problems rather than leaving every existing program unaffected.

Rust Project · Nov 12, 2026

Why it matters

Types can describe impossible states more directly, while an upgrade still deserves compatibility checks.

More context

Update through rustup and run your project’s tests before raising its minimum compiler version. Infallible becomes an alias for the never type. The release also stabilizes core custom-allocator support for Vec and Box; it does not stabilize every planned allocator API.

Keep in mind

Stable compiler release, but older-edition inference can change. If a dependency breaks around never-type fallback, check for a fixed dependency version rather than assuming a compiler regression.

Original read

More engineering ideas, one minute at a time.

Explore more stories