Announcing Rust 1.69.0⚓ Rust 📅 2023-04-20 👤 freedit 👁️ 40
The Rust team is happy to announce a nice version of Rust, 1.69.0. Rust is a programming language empowering everyone to build reliable and efficient software.
If you have a previous version of Rust installed via rustup, you can get 1.69.0 with:
rustup update stable
If you don't have it already, you can get
rustup from the appropriate page on our website, and check out the detailed release notes for 1.69.0 on GitHub.
If you'd like to help us out by testing future releases, you might consider updating locally to use the beta channel (
rustup default beta) or the nightly channel (
rustup default nightly). Please report any bugs you might come across!
What's in 1.69.0 stable
Rust 1.69.0 introduces no major new features. However, it contains many small improvements, including over 3,000 commits from over 500 contributors.
Cargo now suggests to automatically fix some warnings
Rust 1.29.0 added the
cargo fix subcommand to automatically fix some simple compiler warnings. Since then, the number of warnings that can be fixed automatically continues to steadily increase. In addition, support for automatically fixing some simple Clippy warnings has also been added.
In order to draw more attention to these increased capabilities, Cargo will now suggest running
cargo fix or
cargo clippy --fix when it detects warnings that are automatically fixable:
warning: unused import: `std::hash::Hash` --> src/main.rs:1:5 | 1 | use std::hash::Hash; | ^^^^^^^^^^^^^^^ | = note: `#[warn(unused_imports)]` on by default warning: `foo` (bin "foo") generated 1 warning (run `cargo fix --bin "foo"` to apply 1 suggestion)
Note that the full Cargo invocation shown above is only necessary if you want to precisely apply fixes to a single crate. If you want to apply fixes to all the default members of a workspace, then a simple
cargo fix (with no additional arguments) will suffice.
Debug information is not included in build scripts by default anymore
To improve compilation speed, Cargo now avoids emitting debug information in build scripts by default. There will be no visible effect when build scripts execute successfully, but backtraces in build scripts will contain less information.
If you want to debug a build script, you can add this snippet to your
Cargo.toml to emit debug information again:
[profile.dev.build-override] debug = true [profile.release.build-override] debug = true
These APIs are now stable in const contexts:
Check out everything that changed in Rust, Cargo, and Clippy.
Contributors to 1.69.0
Many people came together to create Rust 1.69.0. We couldn't have done it without all of you. Thanks!🏷️ Rust_feed