If you are using a lot of nested indentations, your code becomes rapidly unclear – the pyramid of doom. You can avoid this by using the keyword guard.
The Pyramid Of Doom
Let’s start by looking at an example. We are creating a function that calculates the area of a circle:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 |
enum CircleAreaCalculationError: ErrorType { case RadiusNotSpecified case RadiusUnvalid } func calculateCirlceArea(radius:Double?) throws -> Double { if let radius = radius { if radius > 0 { return radius*radius*M_PI } else { throw CircleAreaCalculationError.RadiusUnvalid } } else { throw CircleAreaCalculationError.RadiusNotSpecified } } |
It is just a very simple example, but it is already very difficult to see what is happening. If the parameter is equal to
nil, the
CircleAreaCalculationError.RadiusUnvalid error will be thrown. Furthermore, if the
radius is not bigger than 0, the
CircleAreaCalculationError.RadiusNotSpecified will be thrown. You can easily imagine how much more difficult the code will be to read, if you are programming a more complex problem.
guard
guard was introduced in Swift 2.0 and it is very powerful.
guard checks whether a certain condition holds true or not. If it doesn’t, you have to leave the current context. So let’s change our code:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 |
enum CircleAreaCalculationError: ErrorType { case RadiusNotSpecified case RadiusUnvalid } func calculateCirleArea(radius:Double?) throws -> Double { guard let radius = radius else { throw CircleAreaCalculationError.RadiusNotSpecified } guard radius > 0 else { throw CircleAreaCalculationError.RadiusUnvalid } return radius*radius*M_PI } |
I my opinion this is much easier to read. Contrary to the example without
guard, the errors are thrown immediately one line after the check and not after a very long
if block. Moreover, the optional
radius becomes a non optional after the
nil check, which makes things a lot easier.
Conclusion
On the first sight
guard seems to be like a very small new feature in Swift 2.0, but it is in fact one of the most important new features in Swift 2.0. References
Swift 2: guard
Wikipedia
Swift 2.0: Why Guard is Better than If
Image: @ Dudarev Mikhail / shutterstock.com
