Rust 1.95: Linear Types and the Future of Memory Safety

**Rust 1.95** has officially reached the stable channel, introducing what many core contributors consider the most significant evolution of the language's ownership model since its 1.0 release: **Linear Types**.

While Rust's affine type system has long ensured that values are used *at most* once, Linear Types go a step further, guaranteeing that a value is used *exactly* once. This enables a new class of compile-time safety for resources that must be explicitly closed or consumed, such as database transactions, file handles, or hardware state machines.

The `MustMove` Trait

At the heart of this feature is the new `MustMove` trait. When a type implements `MustMove`, the compiler will refuse to allow the variable to go out of scope without being consumed by a function that takes ownership of it. This eliminates the "forgot-to-close" class of bugs without the runtime overhead of a `Drop` implementation.

Ergonomic Pinning

Beyond Linear Types, Rust 1.95 provides a massive ergonomic boost to async developers with native **Pin projections**. By integrating projection logic directly into the language, the community can finally move away from complex procedural macros like `pin-project-lite`. This results in faster compile times and significantly cleaner error messages in complex async codebases.

As the ecosystem matures, these features solidify Rust's position as the bedrock of **Infrastructure-as-Software**, where safety and performance are non-negotiable requirements for the next generation of cloud-native foundations.