Rust 1.81: What's New, Release History & Support Lifecycle

What Is New in Rust 1.81

Can I now use the standard Error trait in no_std crates?

Yes, Rust 1.81 stabilizes core::error::Error, allowing you to implement the common Error trait in #![no_std] libraries.

• This unifies error handling across std and no_std ecosystems.
• Existing no_std crates can add impl core::error::Error for MyError { ... } without pulling in the standard library.
• Watch out for any code that still depends on the older std::error::Error trait; replace it with the core version to keep the crate truly no_std.

How do I temporarily silence a lint while still being warned if it disappears?

Use the newly stabilized #[expect] attribute to mark a lint as expected, which will emit a warning if the lint no longer fires.

#[expect(clippy::undocumented_unsafe_blocks)]
fn risky() {
    // unsafe code here
}

• Ideal for incremental migrations where you want to track progress.
• Clippy provides clippy::allow_attributes and clippy::allow_attributes_without_reason to help migrate existing #[allow] attributes.
• In practice, pair #[expect] with a comment explaining the temporary nature of the exemption.

What changes affect sorting and panic handling in Rust 1.81?

Rust 1.81 introduces faster sort algorithms and separates panic hook types, improving both performance and ergonomics.

• Both stable and unstable sort now use new algorithms that reduce runtime and compile-time overhead.
• If an Ord implementation is incorrect, the sort will panic instead of producing nondeterministic order, helping you catch bugs early.
• The panic hook argument type has been renamed to std::panic::PanicHookInfo; the old name remains as an alias but will be deprecated in 1.82.
• Uncaught panics in extern "C" functions now abort the process, closing a long-standing soundness issue. Switch to the "C-unwind" ABI if you rely on unwinding.

Which security and platform updates should I be aware of in Rust 1.81?

Rust 1.81 addresses a Windows command-line vulnerability and updates the WASI target naming.

• std::process::Command now correctly escapes arguments when invoking batch files with trailing whitespace or periods, fixing CVE-2024-43402.
• The legacy wasm32-wasi target now emits a warning; migrate to wasm32-wasip1 to avoid future removal in January 2025.
• These changes are automatic for most codebases, but double-check any custom Windows batch invocation logic and update your Cargo target triples accordingly.