How to check your program state using precondition()
Swift version: 5.6
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.
SPONSORED Join a FREE crash course for mid/senior iOS devs who want to achieve an expert level of technical and practical skills – it’s the fast track to being a complete senior developer! Hurry up because it'll be available only until April 28th.
Sponsor Hacking with Swift and reach the world's largest Swift community!
Available from iOS 8.0 – learn more in my book Pro Swift
Similar solutions…
- How to force your program to crash with assert()
- How to run an external program using Process
- What’s the difference between @ObservedObject, @State, and @EnvironmentObject?
- How to run some code when state changes using onChange()
- How to check whether your other apps are installed
About the Swift Knowledge Base
This is part of the Swift Knowledge Base, a free, searchable collection of solutions for common iOS questions.
