4 ms·
Well, Rust is now at 1.0.0 alpha, which means that the language has almost all of the planned breaking changes implemented (there are still a few corners where
by lambda 12y ago
Well, Rust is now at 1.0.0 alpha, which means that the language has almost all of the planned breaking changes implemented (there are still a few corners where there are a few breaking changes planned, but in things that are minor enough to be unlikely to break much code).
The standard library is still in rapid iteration mode in the preparation for 1.0.0 beta, and thus large portions of it are marked unstable and so only available if you opt-in via a feature gate, but the plan is to stabilize that through the alpha and beta period and have a usable, stable standard library at 1.0.0, which is planned to come out within a few 6-week release cycles from now. And things which are not ready, or not really appropriate for a core standard library, are being moved out into separate Cargo crates that can iterate independently from the core language.
So yes, Rust has been iterating rapidly on the road to 1.0, which makes keeping up with the treadmill painful, but it's finally settling down; very soon you should be able to use it without constant breaking changes.
- steveklabnik 12y ago> in things that are minor enough to be unlikely to break much code). As much as I want this to be true, it's not. `io` is one of those libraries. That's going to break a lot of stuff, probably. Beta is the 'your code will almost absolutely not break' release.
- lambda 12y agoSorry, tried to make that distinction by saying that the language has very few breaking changes left, and those that are left are expected to be minor, but the standard library is still in rapid iteration mode and is expected to break a lot.