From a146ae2f989c322e3ca19d780ce8fa6124f02fcc Mon Sep 17 00:00:00 2001 From: Pietro Albini Date: Sat, 15 Apr 2023 12:32:27 +0200 Subject: [PATCH 1/7] add post for rust 1.69.0 --- posts/2023-04-20-Rust-1.69.0.md | 70 +++++++++++++++++++++++++++++++++ 1 file changed, 70 insertions(+) create mode 100644 posts/2023-04-20-Rust-1.69.0.md diff --git a/posts/2023-04-20-Rust-1.69.0.md b/posts/2023-04-20-Rust-1.69.0.md new file mode 100644 index 000000000..a6734917c --- /dev/null +++ b/posts/2023-04-20-Rust-1.69.0.md @@ -0,0 +1,70 @@ +--- +layout: post +title: "Announcing Rust 1.69.0" +author: The Rust Release Team +release: true +--- + +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: + +```console +rustup update stable +``` + +If you don't have it already, you can [get `rustup`](https://www.rust-lang.org/install.html) from the appropriate page on our website, and check out the [detailed release notes for 1.69.0](https://github.com/rust-lang/rust/blob/master/RELEASES.md#version-1690-2023-04-20) 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](https://github.com/rust-lang/rust/issues/new/choose) any bugs you might come across! + +## What's in 1.69.0 stable + +Rust 1.69.0 doesn't contain major new features. Instead, it focuses on smaller improvements. + +### Cargo now suggests to automatically fix some warnings + +Rust 1.29.0 added a Cargo subcommand to automatically fixing some compilation warnings. Since then, the amount of warnings that can be fixed automatically steadily increased, and support for automatically fixing a subset of Clippy warnings was introduced. + +Starting from Rust 1.69.0, Cargo will suggest running `cargo fix` or `cargo clippy --fix` when it detects some warnings are automatically fixable. + +### 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 need to debug a buggy build script, you can add this snippet to your `Cargo.toml` to emit debug information again: + +```toml +[profile.dev.build-override] +debug = true +[profile.release.build-override] +debug = true +``` + +### Stabilized APIs + +- [`CStr::from_bytes_until_nul`](https://doc.rust-lang.org/stable/core/ffi/struct.CStr.html#method.from_bytes_until_nul) +- [`core::ffi::FromBytesUntilNulError`](https://doc.rust-lang.org/stable/core/ffi/struct.FromBytesUntilNulError.html) + +These APIs are now stable in const contexts: + +- [`SocketAddr::new`](https://doc.rust-lang.org/stable/std/net/enum.SocketAddr.html#method.new) +- [`SocketAddr::ip`](https://doc.rust-lang.org/stable/std/net/enum.SocketAddr.html#method.ip) +- [`SocketAddr::port`](https://doc.rust-lang.org/stable/std/net/enum.SocketAddr.html#method.port) +- [`SocketAddr::is_ipv4`](https://doc.rust-lang.org/stable/std/net/enum.SocketAddr.html#method.is_ipv4) +- [`SocketAddr::is_ipv6`](https://doc.rust-lang.org/stable/std/net/enum.SocketAddr.html#method.is_ipv6) +- [`SocketAddrV4::new`](https://doc.rust-lang.org/stable/std/net/struct.SocketAddrV4.html#method.new) +- [`SocketAddrV4::ip`](https://doc.rust-lang.org/stable/std/net/struct.SocketAddrV4.html#method.ip) +- [`SocketAddrV4::port`](https://doc.rust-lang.org/stable/std/net/struct.SocketAddrV4.html#method.port) +- [`SocketAddrV6::new`](https://doc.rust-lang.org/stable/std/net/struct.SocketAddrV6.html#method.new) +- [`SocketAddrV6::ip`](https://doc.rust-lang.org/stable/std/net/struct.SocketAddrV6.html#method.ip) +- [`SocketAddrV6::port`](https://doc.rust-lang.org/stable/std/net/struct.SocketAddrV6.html#method.port) +- [`SocketAddrV6::flowinfo`](https://doc.rust-lang.org/stable/std/net/struct.SocketAddrV6.html#method.flowinfo) +- [`SocketAddrV6::scope_id`](https://doc.rust-lang.org/stable/std/net/struct.SocketAddrV6.html#method.scope_id) + +### Other changes + +Check out everything that changed in [Rust](https://github.com/rust-lang/rust/blob/stable/RELEASES.md#version-1690-2023-04-20), [Cargo](https://github.com/rust-lang/cargo/blob/master/CHANGELOG.md#cargo-169-2023-04-20), and [Clippy](https://github.com/rust-lang/rust-clippy/blob/master/CHANGELOG.md#rust-169). + +## 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!](https://thanks.rust-lang.org/rust/1.69.0/) From 6647d0ef581c7551395e0bd755d95b7dce3e50ee Mon Sep 17 00:00:00 2001 From: Josh Triplett Date: Mon, 17 Apr 2023 00:37:53 +0900 Subject: [PATCH 2/7] Update posts/2023-04-20-Rust-1.69.0.md Co-authored-by: est31 --- posts/2023-04-20-Rust-1.69.0.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/posts/2023-04-20-Rust-1.69.0.md b/posts/2023-04-20-Rust-1.69.0.md index a6734917c..0b16d92c7 100644 --- a/posts/2023-04-20-Rust-1.69.0.md +++ b/posts/2023-04-20-Rust-1.69.0.md @@ -23,7 +23,7 @@ Rust 1.69.0 doesn't contain major new features. Instead, it focuses on smaller i ### Cargo now suggests to automatically fix some warnings -Rust 1.29.0 added a Cargo subcommand to automatically fixing some compilation warnings. Since then, the amount of warnings that can be fixed automatically steadily increased, and support for automatically fixing a subset of Clippy warnings was introduced. +Rust 1.29.0 added a Cargo subcommand to automatically fix some compilation warnings. Since then, the amount of warnings that can be fixed automatically has steadily increased, and support for automatically fixing a subset of Clippy warnings was introduced. Starting from Rust 1.69.0, Cargo will suggest running `cargo fix` or `cargo clippy --fix` when it detects some warnings are automatically fixable. From 0a4b54876f526b8a9179093ecf6672e71edd3714 Mon Sep 17 00:00:00 2001 From: Josh Triplett Date: Mon, 17 Apr 2023 00:38:08 +0900 Subject: [PATCH 3/7] Update posts/2023-04-20-Rust-1.69.0.md Co-authored-by: est31 --- posts/2023-04-20-Rust-1.69.0.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/posts/2023-04-20-Rust-1.69.0.md b/posts/2023-04-20-Rust-1.69.0.md index 0b16d92c7..8c31e0ee2 100644 --- a/posts/2023-04-20-Rust-1.69.0.md +++ b/posts/2023-04-20-Rust-1.69.0.md @@ -31,7 +31,7 @@ Starting from Rust 1.69.0, Cargo will suggest running `cargo fix` or `cargo clip 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 need to debug a buggy build script, you can add this snippet to your `Cargo.toml` to emit debug information again: +If you want to debug a build script, you can add this snippet to your `Cargo.toml` to emit debug information again: ```toml [profile.dev.build-override] From 7afa2ee0b389ac03705b628fcc2da7a9711114ac Mon Sep 17 00:00:00 2001 From: Pietro Albini Date: Thu, 20 Apr 2023 15:24:31 +0200 Subject: [PATCH 4/7] Update posts/2023-04-20-Rust-1.69.0.md Co-authored-by: bstrie <865233+bstrie@users.noreply.github.com> --- posts/2023-04-20-Rust-1.69.0.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/posts/2023-04-20-Rust-1.69.0.md b/posts/2023-04-20-Rust-1.69.0.md index 8c31e0ee2..04f03240d 100644 --- a/posts/2023-04-20-Rust-1.69.0.md +++ b/posts/2023-04-20-Rust-1.69.0.md @@ -19,7 +19,7 @@ If you'd like to help us out by testing future releases, you might consider upda ## What's in 1.69.0 stable -Rust 1.69.0 doesn't contain major new features. Instead, it focuses on smaller improvements. +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 From 6ff9b22998428b12ddeabc55382cd3d7519d5992 Mon Sep 17 00:00:00 2001 From: Pietro Albini Date: Thu, 20 Apr 2023 15:52:47 +0200 Subject: [PATCH 5/7] Update posts/2023-04-20-Rust-1.69.0.md Co-authored-by: bstrie <865233+bstrie@users.noreply.github.com> --- posts/2023-04-20-Rust-1.69.0.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/posts/2023-04-20-Rust-1.69.0.md b/posts/2023-04-20-Rust-1.69.0.md index 04f03240d..784778cde 100644 --- a/posts/2023-04-20-Rust-1.69.0.md +++ b/posts/2023-04-20-Rust-1.69.0.md @@ -23,7 +23,7 @@ Rust 1.69.0 introduces no major new features. However, it contains many small im ### Cargo now suggests to automatically fix some warnings -Rust 1.29.0 added a Cargo subcommand to automatically fix some compilation warnings. Since then, the amount of warnings that can be fixed automatically has steadily increased, and support for automatically fixing a subset of Clippy warnings was introduced. +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. Starting from Rust 1.69.0, Cargo will suggest running `cargo fix` or `cargo clippy --fix` when it detects some warnings are automatically fixable. From 61a931114bef85c7a543a02f6cdf921fbb93d4c7 Mon Sep 17 00:00:00 2001 From: Pietro Albini Date: Thu, 20 Apr 2023 15:53:12 +0200 Subject: [PATCH 6/7] Update posts/2023-04-20-Rust-1.69.0.md Co-authored-by: bstrie <865233+bstrie@users.noreply.github.com> --- posts/2023-04-20-Rust-1.69.0.md | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/posts/2023-04-20-Rust-1.69.0.md b/posts/2023-04-20-Rust-1.69.0.md index 784778cde..fbc6bb5ff 100644 --- a/posts/2023-04-20-Rust-1.69.0.md +++ b/posts/2023-04-20-Rust-1.69.0.md @@ -25,7 +25,19 @@ Rust 1.69.0 introduces no major new features. However, it contains many small im 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. -Starting from Rust 1.69.0, Cargo will suggest running `cargo fix` or `cargo clippy --fix` when it detects some warnings are automatically fixable. +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 From bb7bd126d51155ae4a3994471bdb87cb90d14c1e Mon Sep 17 00:00:00 2001 From: Pietro Albini Date: Thu, 20 Apr 2023 15:57:06 +0200 Subject: [PATCH 7/7] remove syntax highlighting --- posts/2023-04-20-Rust-1.69.0.md | 20 +++++++++++--------- 1 file changed, 11 insertions(+), 9 deletions(-) diff --git a/posts/2023-04-20-Rust-1.69.0.md b/posts/2023-04-20-Rust-1.69.0.md index fbc6bb5ff..78a8d0985 100644 --- a/posts/2023-04-20-Rust-1.69.0.md +++ b/posts/2023-04-20-Rust-1.69.0.md @@ -27,15 +27,17 @@ Rust 1.29.0 added the `cargo fix` subcommand to automatically fix some simple co 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) +```text +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.