Re:Announcing Rust 1.100.0
by superlupo on Friday November 13, 2026 @02:42AM
(#50479746)
Why not finally a 2.0 if there's a breaking change in it? Or is versioning merely covered by "yearly editions"?
[ Parent
| on HN ]
Re:Announcing Rust 1.100.0
by looperhacks on Friday November 13, 2026 @03:34AM
(#50480204)
Because rust 1.100.0 will still compile older code. To get the breaking changes, a crate has to opt into a newer edition. Older editions will still work fine. Apparently this has the added advantage that crates that use different editions can still work together, because the compiler understands all editions.
The release explicitly made a breaking change for _old_ editions regarding the `Infallible` type. Though they do explain that they consider the fallout of this to be minimal
It's a very minor breaking change. This happens all the time in large projects. E.g. when C++ or Python remove rarely used features. Python would be at version 10 by now if they followed strict backwards compatibility.