Option(al) Is Not A Failure
Swift introduced Optionals on day one, but some of us are still getting used to them. Used appropriately they can be very useful – but they can also be abused!
Swift 1 didn’t have a cohesive error handling strategy. Exceptions were introduced with Swift 2, but remain widely misunderstood.
Should you use Optionals for errors, or exceptions, or something else? Or not bother at all and rely on Bad Things never happening?
How can we make sense of all this when, really, we just want to focus our efforts on getting everything to *work*, not worry about optimising for failures?
This talk digs into what Swift really has to offer and shows it can all be much simpler than we’re making out – and even fun!