You should already know that the
assert() function lets you check the state of your program at runtime, and crash if things aren’t how they should be. One of the neat features of
assert() is that it automatically gets removed when you build your app in release mode, but if you don’t want that to happen – if you want your app to crash if something is seriously wrong – then you should use the
precondition() function instead.
precondition() works identically to
assert(): give it a condition to check along with an optional message to print if the check fails. At runtime – even in release mode – Swift will run the check for you and crash if the check fails.
precondition(users.count > 0, "There must be at least one user.")
assert() should be used liberally to make sure your program is always in a sane state,
precondition() should be used much more infrequently because it will still crash your app in release mode. That’s not always a bad thing, particularly if bad state means something is seriously corrupted, but you should definitely use it more carefully.
Sponsored You’re already busy updating your app for Swift 4.2 and iOS 12, so why not let Instabug help you find and fix bugs? Add just two lines of code to your project and receive comprehensive reports with all the feedback you need to ship a world-class app – click here to learn more!
Available from iOS 8.0 – learn more in my book Pro Swift
Did this solution work for you? Please pass it on!
Other people are reading…
About the Swift Knowledge Base
This is part of the Swift Knowledge Base, a free, searchable collection of solutions for common iOS questions.
Get my latest video for free
Learn about value types, functional programming, and protocol-oriented programming in this new video – it's free!