3 ms·
> If you write code for 1.0 now, it'll compile on a future 1.0 release. Almost: it will compile on all future Rust releases to the end of time (unless Rust wan
by pron 12y ago
> If you write code for 1.0 now, it'll compile on a future 1.0 release.
Almost: it will compile on all future Rust releases to the end of time (unless Rust wants to commit suicide). Languages cannot ever make breaking changes once they reach a stable version (unless they have relatively little adoption). This is even more crucial for "low level" languages like Rust, as they are often used for projects that are meant to last for decades, and are often chosen by programmers who want don't have the patience for this kind of thing.
- TheHydroImpulse 12y agoWith proper tooling, one could automatically upgrade a 1.x Rust compatible codebase to be 2.0 compatible (if such a version ever exists in the future).
- pron 12y agoAFAIK (and it would be interesting to hear of counter examples) that's never been done for a mainstream language before (of course, Rust is far from mainstream -- yet -- but if it never becomes mainstream than it can do whatever it wants, including break backwards compatibility).
- masklinn 12y ago> Almost: it will compile on all future Rust releases to the end of time (unless Rust wants to commit suicide). Languages cannot ever make breaking changes once they reach a stable version (unless they have relatively little adoption). Or nobody expects anything from them (see: PHP)