3 ms·
Editions sound like an interesting riff on C/C++'s standards thing. The post isn't really clear what will be gated behind editions though, only non-BC syntacti
by masklinn 9y ago
Editions sound like an interesting riff on C/C++'s standards thing.
The post isn't really clear what will be gated behind editions though, only non-BC syntactic changes (e.g. literally just new keywords)?
- steveklabnik 9y agoYeah, this post is intended to be a high-level explanation, so we didn't dig into the details. I left a comment below about this: https://news.ycombinator.com/item?id=16569751 https://news.ycombinator.com/item?id=16569751
- masklinn 9y agoOK so non-BC syntactic changes, and warning -> error transitions. Didn't think about the second one but that's way cool. Still, I think it's short and simple enough that it could have been noted in the section, which I feel currently talks about editions a lot but doesn't say much about them.
- Manishearth 9y agoCurrently: - new keywords https://internals.rust-lang.org/t/keywords-to-reserve-for-rust2018-epoch/6720 https://internals.rust-lang.org/t/keywords-to-reserve-for-ru... . There are a lot, but not all of them may end up being used, this is conservatively reserving them. In case a crate on a previous edition has e.g. a method called `catch`, you can still call it via the "raw identifier syntax", `foo.r#catch()` - you can no longer call methods on raw pointers that do not have a fully concrete type in the new epoch. E.g. `foo.is_null()` won't work if `foo` is `const T` and `T` isn't fully known. (This paves the path for `self: const Self`, which may be introduced later).
- geezerjay 9y agoI assumed that the "edition" thing is just an indirect reference to v1.28 or v1.29, just like some linux distros tag the LTS acronym on long term support releases to differentiate them from subsequent intermediate releases. No jab needed, just a codename to refer to the minor version which will be handled as the most stable release and serve as a line in the sand regarding what represents the go-to version for long term projects.
- steveklabnik 9y agoRust 1.29 (for example, not committing to a particular release here) will be able to compile both editions worth of code. Rust 1.300 will still be able to compile Rust 2015. LTS is an entirely different axis. LTS is about artifacts, editions are about the language. I'd really like to see us start an LTS policy this year, but we'll see.