Michael Tsai
Kyle S.
@mjtsai I think that’s directly analogous to ObjC—initializers that return nil are always improved by adding an …error: argument.
-
-
-
@optshiftk Right, but in Objective-C that doesn’t really affect the callsite. -
@mjtsai Adding an …error: argument does affect the callsite. -
@optshiftk The caller can just pass NULL if it doesn’t care. Nothing else changes. With Swift, the caller has to add do-catch blocks. - View other replies
-
@mjtsai Or the caller can prefix with `try!`. Either way, it’s a forced change at the callsite. -
@optshiftk “try!” doesn’t mean “I don’t care about the error details.” It means “I know this will succeed, so crash if it doesn’t.”
-
Nathaniel Irons
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.