3 ms·

Announcing Rust 1.85.0 and Rust 2024

84 points by haakon 2y ago

deleted 2y ago
[deleted]
deleted 2y ago
[deleted]
bitbasher 2y ago
Updated a 16k LOC project and had no issues at all.
GolDDranks 2y ago
This is the hugest release of Rust this far.
Diggsey 2y ago
Huge! Async function traits resolve one of the biggest pain points for async rust.
jenadine 2y ago
We are in 2025 already. Some other tool release their version N at the end of the year N-1.
- jenadine 2y ago
  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.
  - pjmlp 2y ago
    Just like many C code bases are stuck on C89, many Python in Python 2, Java in Java 8, .NET in .NET Framework,... Not that every compiler is up to date, but at very least clang, gcc and vc++ have already quite good coverage of C++20, and clang/vc++ modules mostly work, good enough that I only use modules in my hobby projects. It starts by projects, companies, actually wanting to adopt new toolchains.
- steveklabnik 2y ago
  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.
- satvikpendem 2y ago
  The code was frozen already in 2024, it just took some time to actually release it.
- pjmlp 2y ago
  Same with C23 and C++23, things take time to iron out.
dabinat 2y ago
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.
piotrpdev 2y ago
Unfortunate that they didn't ship the parallel front-end yet, solves my biggest issue with Rust right now.
the__alchemist 2y ago
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 2y ago
  > 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 https://github.com/rust-lang/rustfmt/issues/5083
  - the__alchemist 2y ago
    Thank you for the explanation!
    - steveklabnik 2y ago
      No problem. I have to use nightly for this reason too, haha.

84 points by haakon 2y ago

deleted 2y ago

[deleted]

deleted 2y ago

[deleted]

bitbasher 2y ago

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

GolDDranks 2y ago

This is the hugest release of Rust this far.

Diggsey 2y ago

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

jenadine 2y ago

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

jenadine 2y ago
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.
- pjmlp 2y ago
  Just like many C code bases are stuck on C89, many Python in Python 2, Java in Java 8, .NET in .NET Framework,... Not that every compiler is up to date, but at very least clang, gcc and vc++ have already quite good coverage of C++20, and clang/vc++ modules mostly work, good enough that I only use modules in my hobby projects. It starts by projects, companies, actually wanting to adopt new toolchains.
steveklabnik 2y ago
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.
satvikpendem 2y ago
The code was frozen already in 2024, it just took some time to actually release it.
pjmlp 2y ago
Same with C23 and C++23, things take time to iron out.

dabinat 2y ago

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.

piotrpdev 2y ago

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

the__alchemist 2y ago

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 2y ago
> 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 https://github.com/rust-lang/rustfmt/issues/5083
- the__alchemist 2y ago
  Thank you for the explanation!
  - steveklabnik 2y ago
    No problem. I have to use nightly for this reason too, haha.