Rust release · Apr 16, 2026

Rust 1.95: what's new, what was stabilized

Short answerRust 1.95 was released on Apr 16, 2026: 2 language stabilizations (Stabilize if let guards on match arms); 40 newly stable APIs (MaybeUninit<[T; N]>: From<[MaybeUninit<T>; N]>, MaybeUninit<[T; N]>: AsRef<[MaybeUninit<T>; N]>, MaybeUninit<[T; N]>: AsRef<[MaybeUninit<T>]>, MaybeUninit<[T; N]>: AsMut<[MaybeUninit<T>; N]>, ...); 13 compatibility notes that can affect existing code.

Apr 16, 2026release date

2language stabilizations

40APIs stabilized

-new edition

← Rust 1.94 All versions Rust 1.96 →

Language features stabilized

Stabilize if let guards on match arms
Stabilize inline assembly for PowerPC and PowerPC64

40 APIs stabilized

MaybeUninit<[T; N]>: From<[MaybeUninit<T>; N]>, MaybeUninit<[T; N]>: AsRef<[MaybeUninit<T>; N]>, MaybeUninit<[T; N]>: AsRef<[MaybeUninit<T>]>, MaybeUninit<[T; N]>: AsMut<[MaybeUninit<T>; N]>, MaybeUninit<[T; N]>: AsMut<[MaybeUninit<T>]>, [MaybeUninit<T>; N]: From<MaybeUninit<[T; N]>>, Cell<[T; N]>: AsRef<[Cell<T>; N]>, Cell<[T; N]>: AsRef<[Cell<T>]>, Cell<[T]>: AsRef<[Cell<T>]>, bool: TryFrom<{integer}>, AtomicPtr::update, AtomicPtr::try_update, AtomicBool::update, AtomicBool::try_update, AtomicIn::update, AtomicIn::try_update, AtomicUn::update, AtomicUn::try_update, cfg_select!, mod core::range, core::range::RangeInclusive, core::range::RangeInclusiveIter, core::hint::cold_path, <*const T>::as_ref_unchecked, <*mut T>::as_ref_unchecked, <*mut T>::as_mut_unchecked, Vec::push_mut, Vec::insert_mut, VecDeque::push_front_mut, VecDeque::push_back_mut, VecDeque::insert_mut, LinkedList::push_front_mut, LinkedList::push_back_mut, Layout::dangling_ptr, Layout::repeat, Layout::repeat_packed, Layout::extend_packed, fmt::from_fn, ControlFlow::is_break, ControlFlow::is_continue

Can it break my build?

The release lists these compatibility notes. Most only affect rare code, but read them before you raise your toolchain in CI:

Array coercions may now result in less inference constraints than before
Importing $crate without renaming, i.e. use $crate::{self};, is now no longer permitted due to stricter error checking for self imports.
const-eval: be more consistent in the behavior of padding during typed copies.
A future-incompatibility warning lint ambiguous_glob_imported_traits is now reported when using an ambiguously glob imported trait
Check lifetime bounds of types mentioning only type parameters
Report more visibility-related ambiguous import errors
Deprecate Eq::assert_receiver_is_total_eq and emit future compatibility warnings on manual impls
powerpc64: Use the ELF ABI version set in target spec instead of guessing (fixes the ELF ABI used by the OpenBSD target)
Matching on a #[non_exhaustive] enum now reads the discriminant, even if the enum has only one variant. This can cause closures to capture values that they previously wouldn't.
mut ref and mut ref mut patterns, part of the unstable Match Ergonomics 2024 RFC, were accidentally allowed on stable within struct pattern field shorthand. These patterns are now correctly feature-gated as unstable in this position.
Add future-compatibility warning for derive helper attributes which conflict with built-in attributes
JSON target specs have been destabilized and now require -Z unstable-options to use. Previously, they could not be used without the standard library, which has no stable build mechanism. In preparation for the build-std project adding that support, JSON target specs are being proactively gated to ensure they remain unstable even if build-std is stabilized. Cargo now includes the -Z json-target-spec CLI flag to automatically pass -Z unstable-options to the compiler when needed. See #150151, #151534, and rust-lang/cargo#16557.
[The arguments of #[feature] attributes on invalid targets are now checked](https://github.com/rust-lang/rust/issues/153764)

Use it

rustup update stable        # get the newest release
rustup install 1.95          # or exactly this one
rustup override set 1.95     # pin a project to it

To require at least this version from users of your crate, set rust-version = "1.95" under [package] in Cargo.toml. Cargo then refuses to build it on older compilers with a clear message, and with resolver 3 (the default on the 2024 edition, Rust 1.85+) it also prefers dependency versions that support it.

Full release notes

Language

Stabilize if let guards on match arms
irrefutable_let_patterns lint no longer lints on let chains
Support importing path-segment keywords with renaming
Stabilize inline assembly for PowerPC and PowerPC64
const-eval: be more consistent in the behavior of padding during typed copies
Const blocks are no longer evaluated to determine if expressions involving fallible operations can implicitly be constant-promoted.. Expressions whose ability to implicitly be promoted would depend on the result of a const block are no longer implicitly promoted.
Make operational semantics of pattern matching independent of crate and module

Compiler

Platform Support

Refer to Rust's platform support page for more information on Rust's tiered platform support.

Libraries

Stabilized APIs

[MaybeUninit<[T; N]>: From<[MaybeUninit<T>; N]>](https://doc.rust-lang.org/stable/std/mem/union.MaybeUninit.html#impl-From%3CMaybeUninit%3C%5BT;+N%5D%3E%3E-for-%5BMaybeUninit%3CT%3E;+N%5D)
[MaybeUninit<[T; N]>: AsRef<[MaybeUninit<T>; N]>](https://doc.rust-lang.org/stable/std/mem/union.MaybeUninit.html#impl-AsRef%3C%5BMaybeUninit%3CT%3E;+N%5D%3E-for-MaybeUninit%3C%5BT;+N%5D%3E)
[MaybeUninit<[T; N]>: AsRef<[MaybeUninit<T>]>](https://doc.rust-lang.org/stable/std/mem/union.MaybeUninit.html#impl-AsRef%3C%5BMaybeUninit%3CT%3E%5D%3E-for-MaybeUninit%3C%5BT;+N%5D%3E)
[MaybeUninit<[T; N]>: AsMut<[MaybeUninit<T>; N]>](https://doc.rust-lang.org/beta/std/mem/union.MaybeUninit.html#impl-AsMut%3C%5BMaybeUninit%3CT%3E;+N%5D%3E-for-MaybeUninit%3C%5BT;+N%5D%3E)
[MaybeUninit<[T; N]>: AsMut<[MaybeUninit<T>]>](https://doc.rust-lang.org/stable/std/mem/union.MaybeUninit.html#impl-AsMut%3C%5BMaybeUninit%3CT%3E%5D%3E-for-MaybeUninit%3C%5BT;+N%5D%3E)
[[MaybeUninit<T>; N]: From<MaybeUninit<[T; N]>>](https://doc.rust-lang.org/stable/std/mem/union.MaybeUninit.html#impl-From%3C%5BMaybeUninit%3CT%3E;+N%5D%3E-for-MaybeUninit%3C%5BT;+N%5D%3E)
[Cell<[T; N]>: AsRef<[Cell<T>; N]>](https://doc.rust-lang.org/stable/std/cell/struct.Cell.html#impl-AsRef%3C%5BCell%3CT%3E;+N%5D%3E-for-Cell%3C%5BT;+N%5D%3E)
[Cell<[T; N]>: AsRef<[Cell<T>]>](https://doc.rust-lang.org/stable/std/cell/struct.Cell.html#impl-AsRef%3C%5BCell%3CT%3E%5D%3E-for-Cell%3C%5BT;+N%5D%3E)
[Cell<[T]>: AsRef<[Cell<T>]>](https://doc.rust-lang.org/stable/std/cell/struct.Cell.html#impl-AsRef%3C%5BCell%3CT%3E%5D%3E-for-Cell%3C%5BT%5D%3E)
bool: TryFrom<{integer}>
AtomicPtr::update
AtomicPtr::try_update
AtomicBool::update
AtomicBool::try_update
AtomicIn::update
AtomicIn::try_update
AtomicUn::update
AtomicUn::try_update
cfg_select!
mod core::range
core::range::RangeInclusive
core::range::RangeInclusiveIter
core::hint::cold_path
<*const T>::as_ref_unchecked
<*mut T>::as_ref_unchecked
<*mut T>::as_mut_unchecked
Vec::push_mut
Vec::insert_mut
VecDeque::push_front_mut
VecDeque::push_back_mut
VecDeque::insert_mut
LinkedList::push_front_mut
LinkedList::push_back_mut
Layout::dangling_ptr
Layout::repeat
Layout::repeat_packed
Layout::extend_packed

These previously stable APIs are now stable in const contexts:

Rustdoc

Compatibility Notes

Array coercions may now result in less inference constraints than before
Importing $crate without renaming, i.e. use $crate::{self};, is now no longer permitted due to stricter error checking for self imports.
const-eval: be more consistent in the behavior of padding during typed copies. In very rare cases, this may cause compilation errors due to bytes from parts of a pointer ending up in the padding bytes of a const or static.
A future-incompatibility warning lint ambiguous_glob_imported_traits is now reported when using an ambiguously glob imported trait
Check lifetime bounds of types mentioning only type parameters
Report more visibility-related ambiguous import errors
Deprecate Eq::assert_receiver_is_total_eq and emit future compatibility warnings on manual impls
powerpc64: Use the ELF ABI version set in target spec instead of guessing (fixes the ELF ABI used by the OpenBSD target)
Matching on a #[non_exhaustive] enum now reads the discriminant, even if the enum has only one variant. This can cause closures to capture values that they previously wouldn't.
mut ref and mut ref mut patterns, part of the unstable Match Ergonomics 2024 RFC, were accidentally allowed on stable within struct pattern field shorthand. These patterns are now correctly feature-gated as unstable in this position.
Add future-compatibility warning for derive helper attributes which conflict with built-in attributes
JSON target specs have been destabilized and now require -Z unstable-options to use. Previously, they could not be used without the standard library, which has no stable build mechanism. In preparation for the build-std project adding that support, JSON target specs are being proactively gated to ensure they remain unstable even if build-std is stabilized. Cargo now includes the -Z json-target-spec CLI flag to automatically pass -Z unstable-options to the compiler when needed. See #150151, #151534, and rust-lang/cargo#16557.
[The arguments of #[feature] attributes on invalid targets are now checked](https://github.com/rust-lang/rust/issues/153764)

Internal Changes

These changes do not affect any public interfaces of Rust, but they represent significant improvements to the performance or internals of rustc and related tools.

Update to LLVM 22

Release notes from the Rust project's RELEASES.md (MIT or Apache-2.0); summaries above are ours.