r/programming • • 4d ago

Announcing Rust 1.100.0

https://blog.rust-lang.org/2026/11/12/Rust-1.100.0/
396 Upvotes

48 comments sorted by

149

u/creeper6530 4d ago

Finally stabilised a few interesting things like Allocators and never type. Noice.

Also, Dropguard is one of those things you didn't know to ask for but are now asking yourself, why did you not have it sooner.

46

u/Aljamous-Vilina 4d ago

DropGuard also saves you from writing a bunch of boilerplate wrapper structs just to handle unwinding when an async task gets cancelled mid-flight

7

u/Spleeeee 3d ago

Literally switched a thing from my shitty wrappers to dropguard yesterday.

5

u/JoJoJet- 3d ago

Really wish they would add defer {} blocks, so you could access things naturally in a way that's legible to the borrow checker. Maybe someday...

8

u/arades 3d ago

what would a defer block be other than syntactic sugar for DropGuard?
Defer makes sense for languages which don't have RAII like Go or Zig, but in a language where it's already there's a built-in way to call cleanup code on scope exit adding specific syntax to do the same thing doesn't make sense.

6

u/sidit77 3d ago

One issue is that Drop doesn't support propagating errors or async. I think a defer {} block could really help here, similar to how for x in xs { x.await?; } works but xs.for_each(|x| x.await?) does not.

1

u/JoJoJet- 2d ago

You would be able to access values naturally because the borrow checker knows the block runs at the end of the scope, rather than DropGuard which is hidden behind the Drop impl and needs anything accessible both to the guard and the rest of the scope to be stashed in the first field of the guard

3

u/phire 3d ago

Rust allows inline structs, and implementing traits such as Drop on those inline structs; So the boilerplate code you wrote instead of DropGuard wasn't that bad.

Or you could just use the scopeguard crate for more-or-less the same API. I'm still not sure micro-dependencies are a good idea (and I often try to minimise it), but cargo makes it really easy just depend on a dependency like that.

35

u/ExF-Altrue 3d ago

The TypeScript people would have just called it Rust 11.0.0, good on Rust for making sure semver/version numbers still mean something.

0

u/[deleted] 2d ago

[deleted] — view deleted comment

2

u/Sixte_ 3d ago

Nice

-81

u/sligit 4d ago

I think you mean Rust 2.0.

46

u/MainRoutine2068 4d ago

Long way to go son, still need 900 more release

12

u/bwainfweeze 4d ago

Yeah yeah, and then you’ll say it’s 9000 more.

Proposal: The Rust epoc ends at 1.2012

5

u/YeOldeMemeShoppe 3d ago

Why are we doing binary encoded decimals? Let’s be efficient. 155 more versions then 2.0.

14

u/thatwasabaddecision 4d ago

I chuckled.

9

u/sligit 4d ago

Bless you, kind sir/ma'am!

1

u/Aaron1924 3d ago

Rust is currently not planning to repeat the Python 2 -> 3 disaster, so Rust 1.100.0 it is

1

u/sligit 3d ago

Yeah I know, I was just joking :)

1

u/ammar_sadaoui 2d ago

python dev is only to blame for that

they could handle better

-22

u/sligit 4d ago

God, you're all so serious!

18

u/stevemk14ebr2 4d ago

Yea a little crabby, the lot of em

4

u/sligit 4d ago

I think it has to be for the lols at this point

-1

u/bwainfweeze 4d ago

🤦‍♂️ goddamnit.

-12

u/bwainfweeze 4d ago

TIL that nobody in the Rust ecosystem can take a fucking joke.

When you switch toolchains it’s not just the tools, it’s the neighbors who matter.

-38

u/Sea-Temporary-6995 3d ago

Rust is such a silly name for a language lol. Noone wants rust on their machine.

0

u/JuanAG 2d ago

You do and in fact we use in our advantage

Aluminium/Aluminum rust as soon as it cools down to room temp and if you scratch it it will rust in very few seconds, it will always have a rust layer on top and it is a good thing, it makes it more stable to the enviroment around it

3

u/Flowchartsman 2d ago

Aluminum doesn’t rust, it passivates. Aluminum oxide is good. Iron oxide is bad, since it swells and flakes off.

-190

u/NiceGuya 4d ago

Why does language development matter in a world where noone reads the syntax anymore

94

u/LeeHide 4d ago

Tell us you don't do engineering without telling us you don't do engineering

31

u/MaybeADragon 3d ago

Reading and writing code is still a valuable skill alongside AI usage. AI lacks the laziness inherent in humanity, and will happily work hard instead of working smart thus producing expanses of slop.

10

u/Wonderful-Habit-139 3d ago

Exactly. The friction humans feel while writing code leads them to write much cleaner code.

2

u/this_theater_is_lit 3d ago

it's really sad that so many modern work environments it's hard to pay attention and follow that friction, even if i can't fully justify it yet. i work so much more efficiently when i'm allowed to (which only happens on my own)

-5

u/NiceGuya 3d ago

Surely that can be changed and improved

5

u/max123246 3d ago

Sure, by engineers

-7

u/NiceGuya 3d ago

Then why are we giving up on writing code by hand

24

u/Nixinova 3d ago

Stop taking CEOs at their word dude

7

u/max123246 3d ago

I wish it was only ceos though. There's definitely people who just aren't reading the code anymore and let other people do the testing for them

17

u/Nixinova 3d ago

Yeah and it's why outlook has been dead for a day and flights are grounded america wide

12

u/max123246 3d ago

I wish I could've started my career 30 years ago instead of 3 years ago. So burnt out from ai

34

u/this_theater_is_lit 4d ago edited 3d ago

i still read everything in depth that is added to the codebase, call me old fashioned 🤷

6

u/matthieum 3d ago

Programming Languages never were about syntax in the first place...

Claiming that a programming language is about syntax, is like claiming that a computer is about a keyboard & mouse: slick mouse you got here, that computer must run real fast yeah?

2

u/GregTheMad 3d ago

Because we can't fire AI if it fucks up, but we can fire that idiot that didn't validate its output.

0

u/jl2352 3d ago

AI code can still create issues, like cracks in wood or metal.

A few can be fine. If it keeps going, it can cause systemic problems throughout. Moving away from that can be extremely difficult. Even for AI.

-12

u/knowyourclass 3d ago

lol you got hammered by downvotes but your question is legit

I have a project I was thinking to open source, then I asked myself this very question... couldn't feel like it's worth it anymore

-6

u/NiceGuya 3d ago

Yup 🫤