5 ms·
> [...]every six weeks you'll get this ping, you need assess what changed and whether you need to take action. Rust's stability guarantees mean that you don't
by DasIch 6y ago
> [...]every six weeks you'll get this ping, you need assess what changed and whether you need to take action.
Rust's stability guarantees mean that you don't need to take any action at all.
Breaking changes (unless soundness is involved) only happen with editions and even when a new edition comes out and you update the compiler, you still don't need to do anything unless you explicitly change the configuration of the project to the new edition.
The only thing you might want to do, if you use clippy (a linter that comes with the rust toolchain). Is to check whether it complains about your code due to new check. If that's the case, you get told what to change and why.
- CodesInChaos 6y agoType inference isn't covered by the stability guarantees either, and breaks occasionally.
- steveklabnik 6y agoThe key is that even with places with some wiggle room, like type inference, we take care to try and break as little as possible, sometimes not accepting changes we technically are allowed to, sometimes by adding warnings and waiting a long time... that said, you're right that breakage does sometimes happen here, though we work hard to minimize it, and we don't get tons of complaints that this stuff breaks people's code often.
- pdimitar 6y agoIn the places I worked with Rust it's usually excellently understood that upgrading the compiler must be accompanied by a `clippy` session and a careful review of any and all compiler warnings so IMO compiler upgrade is a non-issue even if there are the very occasional breakages (which I never encountered).