News for hackers. Stuff that matters.
Re:Rust's 2018 roadmap by steveklabnik on Monday March 12, 2018 @01:09PM (#16569594)
You may have noticed a subtle change: what was previously called “epochs” is now “editions.”

Lots of great stuff coming this year! As always, happy to answer any questions.

Re:Rust's 2018 roadmap by squiguy7 on Monday March 12, 2018 @01:36PM (#16569788)
> You can use old editions indefinitely on new compilers; editions are opt-in.

This is great to hear! A best-effort backwards compatibility guarantee is important to have for a language that has a lot of development.

Re:Rust's 2018 roadmap by the_mitsuhiko on Monday March 12, 2018 @01:16PM (#16569634)
What happened to "era"?!
Re:Rust's 2018 roadmap by steveklabnik on Monday March 12, 2018 @01:21PM (#16569673)
In the end, all these words are similar enough that we had to make a call.

We expect most people to say "Rust 2018" and not use any of these terms; we still need one to be the key in Cargo.toml and the flag to the compiler, so we couldn't just use nothing.

Re:Rust's 2018 roadmap by kibwen on Monday March 12, 2018 @01:18PM (#16569649)
The bikeshed works in mysterious ways. :P
Re:Rust's 2018 roadmap by username223 on Monday March 12, 2018 @01:36PM (#16569786)
Era, epoch, edition, excretion, excrescence,... I'm looking forward to watching Rust's continued evolution in the new... whatever they decide to call it.
Re:Rust's 2018 roadmap by the_mitsuhiko on Monday March 12, 2018 @01:39PM (#16569832)
Should have been "cycle" with a fancy name instead of number.
Re:Rust's 2018 roadmap by nothrabannosir on Monday March 12, 2018 @01:55PM (#16569977)
Thanks for keeping to normal, obvious names and reducing the cognitive load. I’m not a fan of unnecessary idiosyncrasies so this is a welcome change.
Re:Rust's 2018 roadmap by pas on Monday March 12, 2018 @02:11PM (#16570120)
For me epoch is more readily associated with new version new features, whereas edition is more like format, such as Mobile edition, Tablet edition, etc.
Re:Rust's 2018 roadmap by cesarb on Monday March 12, 2018 @01:33PM (#16569759)
Could this be used to add an "Ord::clamp" or similar to the stdlib such that it's invisible (and thus wouldn't cause any conflict) to crates with an older "edition"?
Re:Rust's 2018 roadmap by Manishearth on Monday March 12, 2018 @02:24PM (#16570220)
I think for such things it's preferable to just have a `clamp` method as a static method, i.e. you call it with `Ord::clamp(foo, bar)` instead of `foo.clamp(bar)`.

But yes, it could.

Generally the trend seems to be to still try to avoid having actual breakages in the editions unless we _have_ to, and this seems like one of those cases where we don't.

That said, adding Ord::clamp doesn't technically count as a breakage for Rust, Rust's stability guarantee does not include "we added a method to this trait/type and now you have to disambiguate via UFCS" or "we added a thing to this module and now you have to alias your import" because it's not really possible to have that stability guarantee and continue to evolve the stdlib.

That said, given that Ord is in the prelude, the bar for adding stuff to that is much higher. And Rust also cares about the impact of not-technically-breaking changes like these, so we definitely wouldn't just add it as a method.

Re:Rust's 2018 roadmap by aturon on Monday March 12, 2018 @01:38PM (#16569811)
Yes, it could! There aren't plans to do so yet, but it'd be worth spinning up a thread on internals about this.