News for hackers. Stuff that matters.
Re:Announcing Rust 1.14 by steveklabnik on Thursday December 22, 2016 @03:06PM (#13239948)
Small note, we don't _technically have to stabilize Carrier to land this, just implement it for Option. (yay standard library types) However, ? for Option is a bit controversial, so we'll see...
Re:Announcing Rust 1.14 by masklinn on Thursday December 22, 2016 @04:52PM (#13240694)
> However, ? for Option is a bit controversial

Because people wouldn't expect it to return due to behaviour of existing languages yet that's what it does in Rust?

Re:Announcing Rust 1.14 by Rusky on Thursday December 22, 2016 @04:59PM (#13240747)
More because Option is not really intended to handle errors while Result and ? are.
Re:Announcing Rust 1.14 by steveklabnik on Thursday December 22, 2016 @05:07PM (#13240803)
Yes, that's correct. If we make ? go to more than just result, you could implement it for any type, and it's not totally clear that changing it from "error handling" to "general control flow" is a good idea.

Many are in favor of doing it, though. I'm personally against it.

Re:Announcing Rust 1.14 by int_19h on Thursday December 22, 2016 @08:16PM (#13242018)
Whether it's ? or something else, having a very concise form of syntactic sugar to unwrap option types is desirable. Most languages that don't have it, eventually acquire it due to demand.