Lazy evaluation vs eager evaluation in Kotlin - Visual Side-by-Side Comparison

Concept Flow - Lazy evaluation vs eager evaluation

Start

↓

Define Collection

↓

Eager Evaluation

↓

Process All Items Immediately

↓

Result Ready

↓

Lazy Evaluation

↓

Process Items When Needed

↓

Result Computed On Demand

This flow shows how eager evaluation processes all data right away, while lazy evaluation waits and processes data only when needed.

Execution Sample

Kotlin

val numbers = listOf(1, 2, 3, 4)
val eager = numbers.map { println("Eager: $it"); it * 2 }
val lazy = numbers.asSequence().map { println("Lazy: $it"); it * 2 }
lazy.toList()

This code compares eager and lazy evaluation by printing when each item is processed.

Execution Table

Step	Expression	Action	Output	Notes
1	val numbers = listOf(1, 2, 3, 4)	Create list	No output	List created eagerly
2	val eager = numbers.map { println("Eager: $it"); it * 2 }	Map over list eagerly	Eager: 1 Eager: 2 Eager: 3 Eager: 4	All items processed immediately
3	val lazy = numbers.asSequence().map { println("Lazy: $it"); it * 2 }	Create lazy sequence	No output	No processing yet
4	lazy.toList()	Trigger processing of lazy sequence	Lazy: 1 Lazy: 2 Lazy: 3 Lazy: 4	Processing happens now
5	End	Program ends	No output	All lazy items processed on demand

💡 Execution stops after lazy sequence is converted to list, triggering all processing.

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	Final
numbers	[1, 2, 3, 4]	[1, 2, 3, 4]	[1, 2, 3, 4]	[1, 2, 3, 4]	[1, 2, 3, 4]
eager	undefined	[2, 4, 6, 8]	[2, 4, 6, 8]	[2, 4, 6, 8]	[2, 4, 6, 8]
lazy	undefined	undefined	Sequence object	[2, 4, 6, 8]	[2, 4, 6, 8]

Key Moments - 2 Insights

Why does eager evaluation print all items immediately at step 2, but lazy evaluation does not print anything at step 3?

At step 2, map is called on a list, so all items are processed right away, causing prints. At step 3, asSequence creates a lazy sequence that defers processing until needed, so no prints happen yet.

When does the lazy sequence actually process items and print output?

At step 4, calling toList() on the lazy sequence triggers processing of all items, causing the print statements to run.

Visual Quiz - 3 Questions

Look at the execution table, what is the output at step 2?

A No output

B Eager: 1\nEager: 2\nEager: 3\nEager: 4

C Lazy: 1\nLazy: 2\nLazy: 3\nLazy: 4

D Eager: 1 only

💡 Hint

Check the 'Output' column for step 2 in the execution_table.

At which step does the lazy evaluation start processing items?

A Step 4

B Step 3

C Step 2

D Step 1

💡 Hint

Look for when 'Lazy:' print statements appear in the output column.

If we remove lazy.toList(), what happens to the lazy sequence processing?

A It processes immediately at step 3

B It processes at step 2

C It never processes items

D It processes at program end automatically

💡 Hint

Refer to variable_tracker and execution_table step 3 and 4 about when processing happens.

Concept Snapshot

Lazy evaluation delays processing until needed.
Eager evaluation processes immediately.
In Kotlin, sequences are lazy.
List operations are eager.
Use lazy for efficiency with large data.
Call terminal operation to trigger lazy processing.

Full Transcript

This example shows the difference between lazy and eager evaluation in Kotlin. We start with a list of numbers. When we map over the list eagerly, all items are processed and printed immediately. When we create a lazy sequence and map over it, no processing happens until we convert it to a list. This triggers the lazy processing and prints the items. Variables track the state of collections and sequences. Key moments clarify why prints happen at different steps. The quiz tests understanding of when processing occurs and the difference between lazy and eager.

Practice

1. What is the main difference between lazy evaluation and eager evaluation in Kotlin?

easy

A. Lazy evaluation requires manual calls, eager evaluation never runs automatically.

B. Lazy evaluation computes values immediately, eager evaluation delays computation.

C. Lazy evaluation delays computation until the value is needed, eager evaluation computes immediately.

D. Lazy evaluation is only used for variables, eager evaluation only for functions.

Solution

1. Step 1: Understand lazy evaluation

   Lazy evaluation means the program waits to calculate a value until it is actually needed.

2. Step 2: Understand eager evaluation

   Eager evaluation means the program calculates the value right away when the code runs.

3. Final Answer:

   Lazy evaluation delays computation until the value is needed, eager evaluation computes immediately. -> Option C

4. Quick Check:

   Lazy = delay, Eager = immediate [OK]

Hint: Lazy waits, eager runs now. Remember delay vs immediate [OK]

Common Mistakes:

• Confusing which evaluation runs first
• Thinking lazy evaluation runs immediately
• Assuming eager evaluation delays work

2. Which of the following is the correct syntax to declare a lazy property in Kotlin?

easy

A. val x by lazy { 10 }

B. val x = lazy { 10 }

C. lazy val x = 10

D. val x = by lazy 10

Solution

1. Step 1: Recall Kotlin lazy syntax

   Kotlin uses val x by lazy { ... } to declare lazy properties.

2. Step 2: Check each option

   val x by lazy { 10 } matches the correct syntax. The other options are incorrect Kotlin syntax.

3. Final Answer:

   val x by lazy { 10 } -> Option A

4. Quick Check:

   Use 'by lazy { }' for lazy properties [OK]

Hint: Remember: 'val x by lazy { ... }' is correct syntax [OK]

Common Mistakes:

• Using 'lazy val' instead of 'val by lazy'
• Assigning lazy without 'by'
• Placing 'by lazy' after the value

3. What will be the output of the following Kotlin code?

val eager = "Eager".also { println("Eager initialized") }
val lazyVal by lazy { println("Lazy initialized"); "Lazy" }

fun main() {
    println("Start main")
    println(eager)
    println(lazyVal)
    println(lazyVal)
}

medium

A. Start main
Eager initialized
Eager
Lazy initialized
Lazy
Lazy

B. Eager initialized
Start main
Eager
Lazy initialized
Lazy
Lazy

C. Eager initialized
Start main
Eager
Lazy
Lazy initialized
Lazy

D. Start main
Eager
Lazy initialized
Lazy
Lazy initialized
Lazy

Solution

1. Step 1: Understand eager initialization

   The variable eager uses also, so "Eager initialized" prints immediately when declared.

2. Step 2: Understand lazy initialization and main flow

   Lazy variable lazyVal prints "Lazy initialized" only when first accessed. The main prints "Start main", then prints eager (already initialized), then accesses lazyVal twice. The first access triggers initialization print, second does not.

3. Final Answer:

   Eager initialized Start main Eager Lazy initialized Lazy Lazy -> Option B

4. Quick Check:

   Eager prints first, lazy prints on first access [OK]

Hint: Eager prints on declaration, lazy prints on first use [OK]

Common Mistakes:

• Assuming lazy prints before main
• Thinking lazy prints every access
• Mixing order of prints

4. Identify the error in this Kotlin code using lazy evaluation:

val lazyValue by lazy {
    println("Calculating...")
    42
}

fun main() {
    println(lazyValue)
    lazyValue = 50
}

medium

A. Cannot reassign a val property declared with 'by lazy'.

B. Missing parentheses after 'lazy' keyword.

C. Lazy block must return a String, not Int.

D. The println statement inside lazy block is not allowed.

Solution

1. Step 1: Check property mutability

   The property lazyValue is declared with val, meaning it cannot be reassigned after initialization.

2. Step 2: Analyze reassignment in main

   The code tries to assign lazyValue = 50, which is illegal for a val property and causes a compilation error.

3. Final Answer:

   Cannot reassign a val property declared with 'by lazy'. -> Option A

4. Quick Check:

   val lazy properties are read-only, no reassignment [OK]

Hint: val lazy properties cannot be reassigned after initialization [OK]

Common Mistakes:

• Trying to assign a new value to a val lazy property
• Confusing val with var for lazy properties
• Thinking lazy block must return String

5. You want to optimize a Kotlin program that loads a large configuration file only if needed. Which approach best uses lazy evaluation to improve performance?

hard

A. Use a var and assign loadConfig() inside main after checking a flag.

B. Call loadConfig() immediately at program start and store in a val.

C. Declare val config = loadConfig() inside a function that runs every time.

D. Declare the configuration as val config by lazy { loadConfig() } so it loads only on first access.

Solution

1. Step 1: Understand lazy loading benefit

   Loading a large config only when needed saves startup time and resources.

2. Step 2: Choose lazy evaluation syntax

   Using val config by lazy { loadConfig() } delays loading until first use, improving performance.

3. Final Answer:

   Declare the configuration as val config by lazy { loadConfig() } so it loads only on first access. -> Option D

4. Quick Check:

   Lazy loading delays heavy work until needed [OK]

Hint: Use 'by lazy' to delay heavy loading until first use [OK]

Common Mistakes:

• Loading config immediately even if not needed
• Using var without lazy, causing unnecessary loads
• Loading config repeatedly inside functions