Re:Announcing Rust 1.85.0 and Rust 2024
by dabinat on Thursday February 20, 2025 @03:55PM
(#43120072)
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.
Re:Announcing Rust 1.85.0 and Rust 2024
by jenadine on Thursday February 20, 2025 @04:16PM
(#43120319)
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.
Re:Announcing Rust 1.85.0 and Rust 2024
by pjmlp on Thursday February 20, 2025 @06:21PM
(#43121805)
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.
Re:Announcing Rust 1.85.0 and Rust 2024
by steveklabnik on Thursday February 20, 2025 @04:25PM
(#43120419)
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.
Re:Announcing Rust 1.85.0 and Rust 2024
by the__alchemist on Friday February 21, 2025 @03:21PM
(#43132467)
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:
So it may be easier to fix things manually than rely on cargo fix.
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.
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