Series: The Rust Annals
Vol. I Issue 70 nlopes.dev
Announcing Rust 1.69.0
Standard minor release with incremental tooling improvements and API stabilizations, lacking a transformative feature or major version milestone.
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