Rust 2018 is here, but what is it?

Re:Rust 2018 is here, but what is it? by huntie on Thursday December 06, 2018 @02:39PM (#18621315)

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.

[ Parent | on HN ]

Re:Rust 2018 is here, but what is it? by therockhead on Thursday December 06, 2018 @04:05PM (#18622220)

Is this not the situation when any new feature is added to a language?

[ Parent | on HN ]

Re:Rust 2018 is here, but what is it? by steveklabnik on Thursday December 06, 2018 @02:47PM (#18621402)

That’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!

[ Parent | on HN ]

Re:Rust 2018 is here, but what is it? by jononor on Friday December 07, 2018 @12:00PM (#18629280)

If 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?

[ Parent | on HN ]