[swift-evolution] A unified error handling mechanism?
fernando at agbo.biz
Fri Aug 5 18:50:01 CDT 2016
I do a lot of training and one of the features of Swift that seems more
confusing to students (and myself) is error handling. There are too many
ways of doing it, and none seems satisfactory.
Let's take for example an initializer. There are 2 different ways of
handling errors within an init:
a) Old School: return nil. This was very simple in Objective C, because the
uncommon case of an error could be easily ignored...until everything
In Swift it's not easy (nor advisable IMHO) to completely ignore the
possibility of an error. Besides, it has 2 complications.
First of all, you return an Optional, and Optionals have a tendency to go
viral. Suddenly, all your code has to deal with optionals.
Secondly, you have no information about the error itself.
This allows you to have information about the error, but also causes the
newly created object to be "trapped" inside a do block.
Are there any plans to address this situation? I believe there should be a
single, obvious and convenient way of handling errors in the language.
What do you guys think?
m. +34 610 965 332
t. +34 91 629 57 61
fernando at k <fernando at agbo.biz>eepcoding.io
[image: pastedGraphic.png] [image: pastedGraphic_1.png] [image:
2120 University Avenue, Berkeley, CA
Avda. Fuencarral, 44, Ed. 8, Loft 30
28108 Alcobendas (Madrid) Spain
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-evolution