Announcing Rust 1.85.0 and Rust 2024

[dabinat]

I did “cargo fix —-edition” like the guide said and it added the word “ref” before variable names in certain places, which made the compiler complain. So I had to go through and remove them all.

So it may be easier to fix things manually than rely on cargo fix.

[the__alchemist]

Hi! Does anyone know why I still, after updating `rustup` and the `edition` in `Cargo.toml`, need to run `cargo +nightly fmt `? I have a `rustfmt.toml` that contains this:

  imports_granularity = "Crate"
  group_imports = "StdExternalCrate"

I assumed those would be in, as they've been nightly features for years, and we just got a new edition.

[steveklabnik]

> I assumed those would be in,

A new edition doesn't mean features are automatically stabilized.

I agree with these two specifically, it would be great to have them in stable. They're not yet though: https://github.com/rust-lang/rustfmt/issues/5083

[Diggsey]

Huge! Async function traits resolve one of the biggest pain points for async rust.

[bitbasher]

Updated a 16k LOC project and had no issues at all.

[piotrpdev]

Unfortunate that they didn't ship the parallel front-end yet, solves my biggest issue with Rust right now.

[GolDDranks]

This is the hugest release of Rust this far.

[jenadine]

We are in 2025 already. Some other tool release their version N at the end of the year N-1.

[steveklabnik]

From what I understand, when the schedule started to slip, the team made a decision to not do a death march just so it happened two months ago instead of today. This seems healthy to me.

[jenadine]

On the other hand, people will be able to use Rust 2024 in production in a few month, if not now. While most C++ codebase are still stuck with C++17 or older.

[satvikpendem]

The code was frozen already in 2024, it just took some time to actually release it.

[pjmlp]

Same with C23 and C++23, things take time to iron out.