Enum with when exhaustive check in Kotlin - Deep Dive

Overview - Enum with when exhaustive check

What is it?

An enum in Kotlin is a special type that holds a fixed set of constants. The when expression is a control flow structure that lets you choose actions based on values. When used with enums, Kotlin can check if all possible enum values are covered, making the when expression exhaustive. This means you handle every possible case, avoiding mistakes where some enum values are forgotten.

Why it matters

Without exhaustive checks, you might miss handling some enum values, causing bugs or unexpected behavior. Exhaustive when expressions help catch these mistakes at compile time, making your code safer and more reliable. This is especially important in apps where every state or option must be handled correctly, like user roles or app modes.

Where it fits

Before learning this, you should understand basic Kotlin syntax, enums, and the when expression. After mastering this, you can explore sealed classes for more complex exhaustive checks and advanced Kotlin control flow features.

Mental Model

Core Idea

An exhaustive when expression with enums ensures every possible enum value is handled, preventing missing cases.

Think of it like...

It's like checking off every item on a grocery list before leaving the store; you don't want to forget anything important.

┌───────────────┐
│   Enum Type   │
│  (fixed set)  │
└──────┬────────┘
       │
       ▼
┌───────────────┐
│   when(value) │
│ ┌───────────┐ │
│ │ case A    │ │
│ │ case B    │ │
│ │ case C    │ │
│ └───────────┘ │
└───────────────┘
All cases covered → Exhaustive

Build-Up - 6 Steps

1

Foundation

Understanding Kotlin Enums Basics

Concept: Learn what enums are and how to define them in Kotlin.

In Kotlin, an enum class defines a type with a fixed set of constants. For example: enum class Direction { NORTH, SOUTH, EAST, WEST } Each constant represents a possible value of Direction.

Result

You can create variables of type Direction and assign one of the constants, like Direction.NORTH.

Knowing enums lets you represent limited sets of options clearly and safely in your code.

2

Foundation

Using when Expression Basics

Concept: Learn how to use the when expression to choose actions based on values.

The when expression in Kotlin works like a switch-case. Example: val dir = Direction.NORTH when (dir) { Direction.NORTH -> println("Going north") Direction.SOUTH -> println("Going south") else -> println("Other direction") } It matches the value and runs the matching block.

Result

The program prints "Going north" if dir is Direction.NORTH.

When expressions let you write clear, readable code that reacts to different values.

3

Intermediate

Exhaustive when with Enums

🤔Before reading on: do you think Kotlin requires all enum cases in when expressions? Commit to yes or no.

Concept: Kotlin can enforce that when expressions cover all enum values, making them exhaustive.

If you cover all enum constants in when without an else branch, Kotlin treats the when as exhaustive. For example: when (dir) { Direction.NORTH -> println("North") Direction.SOUTH -> println("South") Direction.EAST -> println("East") Direction.WEST -> println("West") } No else is needed because all cases are handled.

Result

The compiler checks all enum values are covered, preventing missing cases.

Exhaustive when expressions catch missing enum cases at compile time, reducing runtime errors.

4

Intermediate

Why else Branch is Needed or Not

🤔Before reading on: If you miss one enum case in when, will Kotlin force you to add else? Commit to yes or no.

Concept: When not all enum cases are covered, Kotlin requires an else branch to handle the rest.

Example missing a case: when (dir) { Direction.NORTH -> println("North") Direction.SOUTH -> println("South") else -> println("Other") } Here, EAST and WEST are not listed, so else covers them. Without else, compiler error occurs.

Result

You must add else or cover all cases to compile successfully.

This rule forces you to think about all enum values, improving code safety.

5

Advanced

Using when as an Expression for Exhaustiveness

🤔Before reading on: Do you think when can return a value only if exhaustive? Commit to yes or no.

Concept: When expressions can return values only if they are exhaustive, ensuring all cases produce a result.

Example: val message = when (dir) { Direction.NORTH -> "Going north" Direction.SOUTH -> "Going south" Direction.EAST -> "Going east" Direction.WEST -> "Going west" } If any case is missing, compiler error occurs because message might not get a value.

Result

You get a guaranteed value from when, avoiding null or uninitialized variables.

Exhaustiveness ensures safe value assignment from when expressions.

6

Expert

Compiler Internals for Exhaustive Check

🤔Before reading on: Do you think Kotlin compiler tracks enum completeness by name or by type? Commit to your answer.

Concept: The Kotlin compiler analyzes the enum type and the when branches to verify all enum constants are covered without else.

At compile time, Kotlin matches each when branch against enum constants. If any constant is missing, and no else is present, it raises an error. This check is part of Kotlin's smart control flow analysis to prevent runtime errors.

Result

Compile-time safety for enum handling without runtime overhead.

Understanding compiler checks helps write safer, cleaner Kotlin code and debug exhaustiveness errors.

Under the Hood

Kotlin's compiler inspects the enum class to get all possible constants. When compiling a when expression on that enum, it compares the branches against these constants. If all constants are matched and no else branch exists, the when is marked exhaustive. This allows when to be used as an expression returning a value safely. If any constant is missing, the compiler demands an else branch to cover the rest. This static check prevents runtime errors from unhandled enum cases.

Why designed this way?

This design was chosen to improve code safety and clarity. Enums represent fixed sets, so the compiler can know all possible values. Enforcing exhaustive when expressions avoids bugs where developers forget to handle some enum cases. Alternatives like requiring else always would reduce safety, and no checks would allow silent bugs. Kotlin balances flexibility and safety by allowing else or full coverage.

┌───────────────┐
│   Enum Class  │
│ ┌───────────┐ │
│ │ Constants │ │
│ │ N, S, E, W│ │
│ └────┬──────┘ │
└──────┼────────┘
       │
       ▼
┌───────────────┐
│  when(expr)   │
│ ┌───────────┐ │
│ │ Branches  │ │
│ │ N, S, E, W│ │
│ └────┬──────┘ │
└──────┼────────┘
       │
       ▼
┌─────────────────────────┐
│ Exhaustive?             │
│ Yes → when is expression │
│ No → else required       │
└─────────────────────────┘

Myth Busters - 4 Common Misconceptions

Quick: Does Kotlin always require an else branch in when expressions with enums? Commit to yes or no.

Common Belief: Kotlin always requires an else branch in when expressions to handle unknown cases.

Reality: Kotlin only requires else if not all enum constants are covered. If all are covered, else is not needed.

Why it matters: Adding unnecessary else branches can hide missing enum cases and reduce code clarity.

Quick: Can you use when as an expression returning a value without covering all enum cases? Commit to yes or no.

Common Belief: You can return a value from when without covering all enum cases if you add else.

Reality: Yes, but the else branch must handle all missing cases. Without else or full coverage, compiler error occurs.

Why it matters: Missing coverage or else causes compile errors, preventing unsafe code.

Quick: Does Kotlin's exhaustive check work with any sealed class the same as enums? Commit to yes or no.

Common Belief: Exhaustive when checks only work with enums, not sealed classes.

Reality: Exhaustive when checks also work with sealed classes, which have a fixed set of subclasses.

Why it matters: Knowing this helps write safer code with sealed classes, not just enums.

Quick: If you add a new enum constant later, will Kotlin warn you about missing when cases? Commit to yes or no.

Common Belief: Kotlin does not warn about missing when cases after adding new enum constants.

Reality: Kotlin will produce a compile error if a when expression is no longer exhaustive after adding new enum constants.

Why it matters: This helps maintain code correctness as enums evolve.

Expert Zone

1

Exhaustive when expressions can be used as statements or expressions, but only expressions require full coverage.

2

When using enums with associated properties or methods, exhaustive checks still only consider constants, not their data.

3

Compiler exhaustiveness checks also work with smart casts and nullable enums, but require careful handling of null cases.

When NOT to use

Avoid relying solely on enums and exhaustive when for very large or dynamic sets of values. Instead, use sealed classes or polymorphism for more flexible hierarchies. Also, if enum values change frequently, exhaustive when can become cumbersome.

Production Patterns

In production Kotlin code, exhaustive when with enums is used to handle state machines, user roles, UI modes, and configuration options. Developers rely on compiler checks to prevent missing cases, improving app stability and maintainability.

Connections

Sealed Classes in Kotlin

Builds-on

Understanding exhaustive when with enums helps grasp sealed classes, which extend this idea to class hierarchies for safer control flow.

Pattern Matching in Functional Languages

Same pattern

Exhaustive checks in Kotlin when expressions are similar to pattern matching in languages like Haskell or Scala, ensuring all cases are handled.

Decision Trees in Machine Learning

Conceptual similarity

Both exhaustive when expressions and decision trees systematically cover all possible cases to make safe, complete decisions.

Common Pitfalls

#1 Missing enum cases in when without else branch

Wrong approach:

when (dir) {
Direction.NORTH -> println("North")
Direction.SOUTH -> println("South")
}
// Missing EAST and WEST, no else branch

Correct approach:

when (dir) {
Direction.NORTH -> println("North")
Direction.SOUTH -> println("South")
Direction.EAST -> println("East")
Direction.WEST -> println("West")
}

Root cause:

Not realizing Kotlin requires all enum constants to be covered or an else branch to compile.

#2 Using else branch unnecessarily when all enum cases are covered

Wrong approach:

when (dir) {
Direction.NORTH -> println("North")
Direction.SOUTH -> println("South")
Direction.EAST -> println("East")
Direction.WEST -> println("West")
else -> println("Unknown")
}

Correct approach:

when (dir) {
Direction.NORTH -> println("North")
Direction.SOUTH -> println("South")
Direction.EAST -> println("East")
Direction.WEST -> println("West")
}

Root cause:

Not knowing that else is optional if all enum cases are handled, leading to redundant code.

#3 Trying to use when as expression without full coverage or else

Wrong approach:

val message = when (dir) {
Direction.NORTH -> "North"
Direction.SOUTH -> "South"
}
// Missing EAST and WEST, no else branch

Correct approach:

val message = when (dir) {
Direction.NORTH -> "North"
Direction.SOUTH -> "South"
Direction.EAST -> "East"
Direction.WEST -> "West"
}

Root cause:

Not understanding that when expressions must be exhaustive to return a value.

Key Takeaways

Kotlin enums represent fixed sets of constants, perfect for limited options.

The when expression lets you choose actions based on values, and can be exhaustive with enums.

Exhaustive when expressions require all enum cases to be handled or an else branch, improving safety.

Using when as an expression demands exhaustiveness to guarantee a return value.

Kotlin's compiler enforces these rules to prevent bugs from missing enum cases, making your code more reliable.