[swift-evolution] Remove Failable Initializers

Kyle Sherman kyledsherman at gmail.com
Thu Mar 3 09:22:24 CST 2016

Oh. I missed that. Thanks. Then I guess I could go either way. Keeping failable initializers, in that case, would be fine and makes sense. 

Sent from my iPhone

> On Mar 3, 2016, at 12:55 AM, Brent Royal-Gordon <brent at architechies.com> wrote:

> I have found that failable initializers really don’t fit in well with Swift’s strict initialization rules (which I think are great). Every time I tried to use them I always had to make sacrifices with having an implicitly unwrapped optional or optional when I shouldn’t.

Are you talking about the "All stored properties of a class instance must be initialized before returning nil from an initializer" error? Because that's being fixed in Swift 2.2.

Brent Royal-Gordon

More information about the swift-evolution mailing list