Wednesday 18 November 2026 Edition compiled at 07.45 NL EN FR
← Tech · Programming languages
Tech · Programming languagesRust

After ten years and five failed attempts, the exclamation mark is a full type in Rust, and Cargo makes brand-new packages wait a while

Rust 1.100 stabilises the never type and the Allocator API, and gives developers a waiting period as a buffer against compromised packages.

· latest source update do · 2 sources · Rust Blog, DEV Community
Illustration for this article

The Rust team released version 1.100 of the programming language last Thursday. The most important change, according to the official announcement, is that the never type, written as an exclamation mark, may now be used as a type anywhere, for example in a Result that can never contain an error. The type stands for a value that can never exist, such as the outcome of a function that exits the program. The existing Infallible is now an alias for it.

It has taken a long time. A developer on DEV Community recalls that the proposal was submitted in July 2016 and that five earlier attempts to stabilise it failed. The stumbling block was that the compiler had to choose a different default type in some cases, which could change existing code. Initial tests on crates.io turned up 3,277 problems. That is why the change first arrived in the 2024 edition and now applies to all editions. The team warns that the compiler may therefore flag code as unreachable more often.

The standard library is growing too. The Allocator trait, which lets programs decide for themselves how memory is allocated, is stable and works with Vec and Box. New additions include DropGuard, which runs a piece of code when a value is cleaned up, and smaller helper functions such as bool::toggle and Vec::from_fn.

Package manager Cargo gets two notable features. It now reports dependencies that are not used, and with the global-min-publish-age setting developers can skip freshly published versions for a while during automatic updates. According to the DEV author, malicious versions are often discovered within hours or days, and that waiting period is meant to bridge the window. The Rust team calls it useful but incomplete protection.

Spotted a mistake in this article? Let us know.