3 ms·
The former is not about a feature that requires Rust 2018. So the latter does not apply to it at all.
by steveklabnik 8y ago
The former is not about a feature that requires Rust 2018. So the latter does not apply to it at all.
- Dylan16807 8y agoBut just like you can add a "Rust 2015" feature after 2015, you can add a "Rust 2018" feature after 2018, right? If yes, then how do you best distinguish "Rust 2018 with additions" from "Rust 2018, the original 2018 version"? If no, then there are some extremely misleading descriptions of what an 'edition' is, because they don't mention that 2015 is special.
- steveklabnik 8y ago> But just like you can add a "Rust 2015" feature after 2015, you can add a "Rust 2018" feature after 2018, right? You cannot, no. > there are some extremely misleading descriptions of what an 'edition' is Where? I am sorry you're this confused. I don't think I know how to explain this to you.
- Dylan16807 8y agoLet me quote https://blog.rust-lang.org/2018/07/27/what-is-rust-2018.html https://blog.rust-lang.org/2018/07/27/what-is-rust-2018.html "Beyond that, it’s also important to mention that this release will be the initial release of Rust 2018; in some sense, it’s the start, not the end. We haven’t formally committed to a schedule for editions, but it’s likely that the next one will be Rust 2021. We’ll continue to add features to Rust 2018 after its release, just like we continued to add features to Rust after the Rust 1.0 release. "It’s also important to note that Rust 2015 is not frozen. Anything that does not require being a part of Rust 2018 will work on Rust 2015 as well. This is due to the way editions work; given the small nature of possible changes, the compiler uses the same internal representation for all editions." That seems to directly contradict your first answer. Is there some subtlety I'm missing?
- irishsultan 8y ago>> But just like you can add a "Rust 2015" feature after 2015, you can add a "Rust 2018" feature after 2018, right? > You cannot, no. So let's assume I think of a new syntax which is compatible with existing Rust 2018 code, but which is syntactic sugar for async code (so not compatible with Rust 2015 code). Are you saying that this can not be added until Rust 2021 comes along? Or are you saying that you can add it but it won't be Rust 2018? If the latter is the case I think it's really confusing to call impl_header_lifetime_elision a Rust 2015 feature.
- steveklabnik 8y agoIf it’s compatible with Rust 2018, then there’s no reason it couldn’t be in Rust 2018. Only breaking stuff needs to wait until the next edition. It’s really not clear to me what exactly you’re proposing, but it sounds like breaking syntax, and so yes, it would have to wait.
- irishsultan 8y ago> If it’s compatible with Rust 2018, then there’s no reason it couldn’t be in Rust 2018. Only breaking stuff needs to wait until the next edition. That sounds like Rust 2018 would get a new feature, something that sounds in contradiction with a feature freeze. > It’s really not clear to me what exactly you’re proposing, but it sounds like breaking syntax, and so yes, it would have to wait. I was trying to clarify things by proposing a particular situation, a non-breaking syntax change, so I'm not sure how that could possibly sound like breaking syntax. If you believe it's impossible for syntactic sugar to be introduced with backwards compatibility then how do you explain the question mark operator for Error handling?
- steveklabnik 8y agoAgain, the “freeze” is for 2018 specific features, the ones that would be backwards incompatible with 2015. ? isn’t sugar, and also isn’t a breaking change.
- 8y ago