20 ms·
That's just blatantly false. Rust takes extreme pains to be backwards compatible. When they wanted to make breaking changes to support some new language feature
by carlosdp 5y ago
That's just blatantly false. Rust takes extreme pains to be backwards compatible. When they wanted to make breaking changes to support some new language features, they literally spun up a separate compiler front-end behind a cargo.toml flag to make sure they didn't break any existing code.
Compiler changes are tested against a bunch of libraries in the crates.io repository to ensure nothing breaks. It's just exceedingly rare that a new Rust version would break older code.
- ithkuil 5y agoI think GP meant forward compatibility. New code will use new features and won't compile on old compilers (like other languages)
- Ar-Curunir 5y agoIf you updated old compiler with new features, aren't they new compilers?
- ithkuil 5y agothe most charitable reading of GP is not that nobody can ever implement new features in a language but that the 5 month release cycle is causing new features to come in too fast.