3 ms·
> any Github Rust project not updated in the last two years doesn't work with the latest Rust compiler. I don't think this is correct? Rust introduced an "edit
by 0815test 8y ago
> any Github Rust project not updated in the last two years doesn't work with the latest Rust compiler.
I don't think this is correct? Rust introduced an "editions"-based system in 2015, with the very aim of ensuring forward compatibility on a crate-by-crate basis. The aim is definitely that any crate written to be compatible with some "edition of Rust", whether 2015, 2018 or whatever, can be made to compile on a future version of the compiler.
- db48x 8y agoOne possibility is that he used something written against the nightly Rust compiler. That code would be very unlikely to compile today.
- 0815test 8y agoMaybe, but you have to specifically opt-in to the nightly toolchain in order to compile something that uses it. It's not something that's included by default, or appropriate for use in production scenarios (unless you're willing to deal with the resulting breakage, of course).
- db48x 8y agoOf course it's not suitable for production, but it was still quite common to look at a rust project and find that it used the nightly compiler.
- paulddraper 8y agoIt's been awhile, but if memory serves tons of stuff was using the nightly compiler. So, yes buyer beware. But when the whole ecosystem does it...
- db48x 8y agoExactly. I think it's getting better now that some of the cool things people were waiting on have made it into the 2018 edition. Off-hand I know that Remacs switched from the nightlies to 2018.