Announcing Rust 1.85.0 and Rust 2024 | Rust Blog
(blog.rust-lang.org)
from thingsiplay@beehaw.org to programming@programming.dev on 20 Feb 17:14
https://beehaw.org/post/18560241
from thingsiplay@beehaw.org to programming@programming.dev on 20 Feb 17:14
https://beehaw.org/post/18560241
Finally the new Rust 1.85.0 update is here, with a new Rust Edition 2024.
#programming
threaded - newest
BTW no word about the Next Gen Trait solver: …rust-lang.org/…/trait-solving.html
Road to 2027 then?
It was mentioned in the notes for 1.84.0 that they began migrating to it. They might be doing it without an edition change if it’s backwards compatible (or if the incompatibilities are considered bugs).
Honestly, kind of most excited about
std::env::home_dir()
being fixed/undeprecated. That’s the kind of thing that some languages would leave unfixed for eternity, until half the community recommends not using the stdlib even for basic uses.So glad they made the sane move and fixed
std::env::home_dir()
. The previous situation of having it deprecated due to fairly insignificant reasons, while recommending an abandoned crate instead was just silly.The
gen
keyword is too much teasing, I know it’s not round the corner but I’m gonna explode 🥺In case the wording tripped anyone, generators (blocks and functions) have been available for a while as an unstable feature.
This works (playground):
Note that the block-in-fn version works better at this moment (from a developer’s PoV) because
rust-analyzer
currently treatsgfn()
as an i32 value. But the block-in-fn pattern works perfectly already.Amazing! Thanks for that. I didn’t know this was actually available to play with.
I love the async closure update and the if-let scoping fix.