4 ms·
Sure, I understand that. But if I've only ever used Rust 2018 and I go to submit a PR to the regex crate, I now need to be aware of any differences between the
by huntie 8y ago
Sure, I understand that. But if I've only ever used Rust 2018 and I go to submit a PR to the regex crate, I now need to be aware of any differences between the two versions.
It might not be a big deal, but a few weeks ago I started a new project that was going to reuse code from an existing project. The new project defaulted to 2018 (nightly compiler) and I got a bunch of errors with my module imports. It was just frustrating because it felt like it was a breaking change and one of the reasons I started using Rust is the promise of no breaking changes.
- steveklabnik 8y agoThat’s fair! These kinds of changes are generally on par with other “never break” languages like Java and C++. Java 1.4 feels very different than Java 10. It’s tough!
- therockhead 8y agoIs this not the situation when any new feature is added to a language?
- jononor 8y agoIf you want to use Rust 2015, just do so? I fail to see how Rust editions could be much smoother managed. Or should they never fix anything in the language?