Rust versions / 1.61
Rust release · May 19, 2022
Rust 1.61: what's new, what was stabilized
Short answerRust 1.61 was released on May 19, 2022: 17 newly stable APIs (Pin::static_mut, Pin::static_ref, Vec::retain_mut, VecDeque::retain_mut, ...); 8 compatibility notes that can affect existing code.
← Rust 1.60All versionsRust 1.62 →
17 APIs stabilized
Pin::static_mut, Pin::static_ref, Vec::retain_mut, VecDeque::retain_mut, Write, std::os::unix::net::SocketAddr::from_pathname, std::process::ExitCode, std::thread::JoinHandle::is_finished, <*const T>::offset, <*const T>::wrapping_offset, <*const T>::add, <*const T>::sub, <*const T>::wrapping_add, <*const T>::wrapping_sub, <[T]>::as_mut_ptr, <[T]>::as_ptr_range, <[T]>::as_mut_ptr_range
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:
- Previously native static libraries were linked as
whole-archivein some cases, but now rustc tries not to usewhole-archiveunless explicitly requested. This [change][93901] may result in linking errors in some cases. To fix such errors, native libraries linked from the command line, build scripts, or [#[link]attributes][link-attr] need to - [Catching a second unwind from FFI code while cleaning up from a Rust panic now causes the process to abort][92911]
- [Proc macros no longer see
identmatchers wrapped in groups][92472] - [The number of
#inr#raw string literals is now required to be less than 256][95251] - [When checking that a dyn type satisfies a trait bound, supertrait bounds are now enforced][92285]
- [
cargo vendornow only accepts one value for each--syncflag][cargo/10448] - [
cfgpredicates inall()andany()are always evaluated to detect errors, instead of short-circuiting.][94295] The compatibility considerations here arise in nightly-only code that used the short-circuiting behavior ofallto write something likecfg(all(feature = "nightly", syntax-requiring-nightly)), which will now fail to compile. Instead, use eithercfg_attr(feature = "nightly", ...)or nested uses ofcfg. - [bootstrap: static-libstdcpp is now enabled by default, and can now be disabled when llvm-tools is enabled][94832]
Use it
rustup update stable # get the newest release
rustup install 1.61 # or exactly this one
rustup override set 1.61 # pin a project to itTo require at least this version from users of your crate, set rust-version = "1.61" 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
- [
const fnsignatures can now include generic trait bounds][93827] - [
const fnsignatures can now useimpl Traitin argument and return position][93827] - [Function pointers can now be created, cast, and passed around in a
const fn][93827] - [Recursive calls can now set the value of a function's opaque
impl Traitreturn type][94081]
Compiler
- [Linking modifier syntax in
#[link]attributes and on the command line, as well as thewhole-archivemodifier specifically, are now supported][93901] - [The
chartype is now described as UTF-32 in debuginfo][89887] - The [
#[target_feature]][target_feature] attribute [can now be used with aarch64 features][90621] - X86 [
#[target_feature = "adx"]is now stable][93745]
Libraries
- [
ManuallyDrop<T>is now documented to have the same layout asT][88375] - [
#[ignore = "…"]messages are printed when running tests][92714] - [Consistently show absent stdio handles on Windows as NULL handles][93263]
- [Make
std::io::stdio::lock()return'statichandles.][93965] Previously, the creation of locked handles to stdin/stdout/stderr would borrow the handles being locked, which prevented writinglet out = std::io::stdout().lock();becauseoutwould outlive the return value ofstdout(). Such code now works, eliminating a common pitfall that affected many Rust users. - [
Vec::from_raw_partsis now less restrictive about its inputs][95016] - [
std::thread::available_parallelismnow takes cgroup quotas into account.][92697] Sinceavailable_parallelismis often used to create a thread pool for parallel computation, which may be CPU-bound for performance,available_parallelismwill return a value consistent with the ability to use that many threads continuously, if possible. For instance, in a container with 8 virtual CPUs but quotas only allowing for 50% usage,available_parallelismwill return 4.
Stabilized APIs
- [
Pin::static_mut] - [
Pin::static_ref] - [
Vec::retain_mut] - [
VecDeque::retain_mut] - [
WriteforCursor<[u8; N]>][cursor-write-array] - [
std::os::unix::net::SocketAddr::from_pathname] - [
std::process::ExitCode] and [std::process::Termination]. The stabilization of these two APIs now makes it possible for programs to return errors frommainwith custom exit codes. - [
std::thread::JoinHandle::is_finished]
These APIs are now usable in const contexts:
- [
<*const T>::offsetand<*mut T>::offset][ptr-offset] - [
<*const T>::wrapping_offsetand<*mut T>::wrapping_offset][ptr-wrapping_offset] - [
<*const T>::addand<*mut T>::add][ptr-add] - [
<*const T>::suband<*mut T>::sub][ptr-sub] - [
<*const T>::wrapping_addand<*mut T>::wrapping_add][ptr-wrapping_add] - [
<*const T>::wrapping_suband<*mut T>::wrapping_sub][ptr-wrapping_sub] - [
<[T]>::as_mut_ptr][slice-as_mut_ptr] - [
<[T]>::as_ptr_range][slice-as_ptr_range] - [
<[T]>::as_mut_ptr_range][slice-as_mut_ptr_range]
Cargo
No feature changes, but see compatibility notes.
Compatibility Notes
- Previously native static libraries were linked as
whole-archivein some cases, but now rustc tries not to usewhole-archiveunless explicitly requested. This [change][93901] may result in linking errors in some cases. To fix such errors, native libraries linked from the command line, build scripts, or [#[link]attributes][link-attr] need to - (more common) either be reordered to respect dependencies between them (if
adepends onbthenashould go first andbsecond) - (less common) or be updated to use the [
+whole-archive] modifier. - [Catching a second unwind from FFI code while cleaning up from a Rust panic now causes the process to abort][92911]
- [Proc macros no longer see
identmatchers wrapped in groups][92472] - [The number of
#inr#raw string literals is now required to be less than 256][95251] - [When checking that a dyn type satisfies a trait bound, supertrait bounds are now enforced][92285]
- [
cargo vendornow only accepts one value for each--syncflag][cargo/10448] - [
cfgpredicates inall()andany()are always evaluated to detect errors, instead of short-circuiting.][94295] The compatibility considerations here arise in nightly-only code that used the short-circuiting behavior ofallto write something likecfg(all(feature = "nightly", syntax-requiring-nightly)), which will now fail to compile. Instead, use eithercfg_attr(feature = "nightly", ...)or nested uses ofcfg. - [bootstrap: static-libstdcpp is now enabled by default, and can now be disabled when llvm-tools is enabled][94832]
Internal Changes
These changes provide no direct user facing benefits, but represent significant improvements to the internals and overall performance of rustc and related tools.
Release notes from the Rust project's RELEASES.md (MIT or Apache-2.0); summaries above are ours.
Up next
Next releaseRust 1.62Released Jun 30, 2022.Read it next →Also worth your time
Did this answer your question?