[swift-evolution] [Review] SE-0054: Abolish ImplicitlyUnwrappedOptional type

Cheyo Ximenez cheyo at masters3d.com
Fri Mar 25 16:10:03 CDT 2016

>    * What is your evaluation of the proposal?
This is a great idea. I actually feel that I understand IUO much better in this proposal than in the previous model. I do have a question. 

let x: Int! = 5
let y = x

let a = x ?? 1 // would this still work? 
Or would it auto unwrapping always? meaning when .some `a = 5` or crash when .none? 
I am assuming that x is `Int?` that autounwraps. Just curious if autounwraps only happen on assignment like in `y = x`

>    * Is the problem being addressed significant enough to warrant a change to Swift?
I believe so, it makes IUO feel more like an automatic behavior on regular optionals. 
>    * Does this proposal fit well with the feel and direction of Swift?
Yes embracing change while still supporting portable code. 
>    * If you have you used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?
I've only used this with swift. 
>    * How much effort did you put into your review? A glance, a quick reading, or an in-depth study?
Read the proposal and followed tread

More information about the swift-evolution mailing list