> How do you guys think of that?
Makes sense.
Failable init has its roots in Objective-C, throws is a better fit for Swift —
but it is not trivial to change all Cocoa class to throw instead of returning
nil (at least in theory — most likely many classes don't have that many reasons
for a possible error).
Imho failable init should be removed again (but in a timeframe beyond the
normal range of this list ;-)
Tino
_______________________________________________
swift-evolution mailing list
[email protected]
https://lists.swift.org/mailman/listinfo/swift-evolution
