News for hackers. Stuff that matters.
Re:Announcing Rust 1.7 by kibwen on Thursday March 03, 2016 @02:34PM (#11219367)
As mentioned in the OP, Rust really hasn't added any language-level features since 1.0, but looking forward there were two major features whose RFCs were accepted this cycle: impl specialization (https://github.com/rust-lang/rfcs/pull/1210#issuecomment-187...) and the `?` operator (https://github.com/rust-lang/rfcs/pull/243#issuecomment-1805...). The former will keep code from having to pay a de facto performance penalty for being generic (preliminary implementation at https://github.com/rust-lang/rust/pull/30652), and the latter is purely an ergonomic change to make our `Result`-based error handling more lightweight (preliminary implementation at https://github.com/rust-lang/rust/pull/31954).

I'm personally hoping the latter one manages to get into the beta release for the next cycle, so that I can use `?` rather than `try!()` for my Rust tutorial at OSCON this year. :)

Re:Announcing Rust 1.7 by steveklabnik on Thursday March 03, 2016 @02:41PM (#11219427)
Well, beta for the _next_ release is already branched; it would be the one after that, at the earliest.
Re:Announcing Rust 1.7 by kibwen on Thursday March 03, 2016 @02:59PM (#11219559)
1.8-beta has branched, yes, but if it stabilizes this cycle it would make it into 1.9-beta (which would progress to 1.9-stable the week after OSCON), and our beta releases have proven themselves stable enough that I'm perfectly happy to use them in tutorials.
Re:Announcing Rust 1.7 by tatterdemalion on Thursday March 03, 2016 @03:29PM (#11219776)
I would be surprised if ? were stabilized in the next 6 weeks after how contentious the RFC was.
Re:Announcing Rust 1.7 by steveklabnik on Thursday March 03, 2016 @03:30PM (#11219784)
Yes, I expect it to move more slowly than an immediate stabilization as well.
Re:Announcing Rust 1.7 by kibwen on Thursday March 03, 2016 @03:44PM (#11219901)
Alas, you're probably right. :) A man can dream!