What if missing just one case could crash your app? Swift's exhaustive switch saves you from that nightmare!
Why Switch must be exhaustive in Swift? - Purpose & Use Cases
Imagine you have a list of all possible fruits, and you want to write code that does something different for each fruit. You try to write a simple switch statement but forget to cover some fruits.
When you miss some fruits, your program might crash or behave unpredictably. You have to remember every single fruit manually, which is tiring and easy to forget. This leads to bugs and wasted time fixing them.
Swift's switch must be exhaustive, meaning you have to cover all possible cases or provide a default. This forces you to think about every option, making your code safer and more reliable.
switch fruit {
case "apple":
print("Apple selected")
// forgot other fruits
}switch fruit {
case "apple":
print("Apple selected")
case "banana":
print("Banana selected")
case "orange":
print("Orange selected")
default:
print("Unknown fruit")
}This ensures your program handles every possible case, preventing unexpected crashes and making your code bulletproof.
Think of a vending machine that must respond correctly to every button press. Exhaustive switches guarantee it never ignores a button, so customers always get what they expect.
Exhaustive switches prevent missing cases and bugs.
They force you to handle all possibilities or provide a fallback.
This leads to safer, more predictable programs.
Practice
switch statement must be exhaustive?Solution
Step 1: Understand the meaning of exhaustive switch
In Swift, a switch must cover every possible value of the variable it checks to avoid missing cases.Step 2: Compare options to definition
Only It must handle all possible values of the variable being switched on. states that all possible values must be handled, which matches the requirement.Final Answer:
It must handle all possible values of the variable being switched on. -> Option AQuick Check:
Exhaustive means all cases covered = A [OK]
- Thinking switch can skip cases
- Believing only first match matters
- Assuming minimum number of cases
switch statements is syntactically correct and exhaustive for an enum Direction with cases north, south, east, and west?Solution
Step 1: Check all enum cases covered
The enum has four cases: north, south, east, west. The switch must cover all or use default.Step 2: Analyze each option
switch dir { case .north: print("North") case .south: print("South") case .east: print("East") case .west: print("West") } covers all four cases explicitly, making it exhaustive and syntactically correct.Final Answer:
switch with all four cases covered explicitly -> Option BQuick Check:
All enum cases covered = D [OK]
- Missing some enum cases
- Not using default when cases are incomplete
- Assuming partial cases are enough
enum Mood { case happy, sad, neutral }
let todayMood = Mood.sad
switch todayMood {
case .happy: print("Feeling great!")
case .sad: print("Feeling down.")
case .neutral: print("Just okay.")
}Solution
Step 1: Identify the value of todayMood
todayMood is set to Mood.sad.Step 2: Match the switch case
The switch has a case for .sad that prints "Feeling down." so this case runs.Final Answer:
Feeling down. -> Option CQuick Check:
Value sad matches case sad = B [OK]
- Confusing cases and printing wrong output
- Thinking switch is not exhaustive here
- Ignoring the actual value assigned
Color with cases red, green, and blue:switch color {
case .red: print("Red")
case .green: print("Green")
}Solution
Step 1: Check all enum cases handled
The enum has three cases: red, green, blue. The switch only handles red and green.Step 2: Identify missing coverage
Since .blue is missing and no default case is provided, the switch is not exhaustive, causing a compile error.Final Answer:
Missing case for .blue or default case, so switch is not exhaustive. -> Option DQuick Check:
All cases must be covered or default = C [OK]
- Ignoring missing enum cases
- Thinking parentheses needed after switch
- Confusing raw values with case coverage
enum Status { case success, failure, unknown }
let currentStatus = Status.unknown
switch currentStatus {
case .success: print("Success")
case .failure: print("Failure")
}Solution
Step 1: Understand the problem with current switch
The switch handles .success and .failure but misses .unknown, so it's not exhaustive.Step 2: Find a way to cover missing cases without listing all explicitly
Adding a default case covers any cases not explicitly handled, making the switch exhaustive.Final Answer:
Add a default case to handle all other values. -> Option AQuick Check:
Use default to cover missing cases = A [OK]
- Thinking you must list every case explicitly
- Removing switch instead of fixing it
- Changing enum just to fix switch
Ready to prove it?
Pass the test and this pattern moves unknown
