NEW! Master Swift design patterns with my latest book! >>

How to check your program state using precondition()

Paul Hudson       @twostraws

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.

For example:

precondition(users.count > 0, "There must be at least one user.")

Whereas 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.

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.

Build for watchOS

Take your existing Swift skills to Apple's tiniest platform – check out Hacking with watchOS!

MASTER SWIFT NOW
Buy Practical iOS 12 Buy Pro Swift Buy Swift Design Patterns Buy Practical iOS 11 Buy Swift Coding Challenges Buy Server-Side Swift (Vapor Edition) Buy Server-Side Swift (Kitura Edition) Buy Hacking with macOS Buy Advanced iOS Volume One Buy Hacking with watchOS Buy Hacking with tvOS Buy Hacking with Swift Buy Dive Into SpriteKit Buy Swift in Sixty Seconds Buy Objective-C for Swift Developers Buy Beyond Code

Was this page useful? Let me know!

Click here to visit the Hacking with Swift store >>