Lazy evaluation vs eager evaluation in Kotlin - Performance Comparison

Time Complexity: Lazy evaluation vs eager evaluation

O(n)

Understanding Time Complexity

We want to see how lazy and eager evaluation affect how long a program takes to run.

Specifically, how does the way values are computed change the work done as input grows?

Scenario Under Consideration

Analyze the time complexity of the following Kotlin code using lazy and eager lists.

val eagerList = (1..n).map { it * 2 }
val lazySequence = (1..n).asSequence().map { it * 2 }
val eagerSum = eagerList.sum()
val lazySum = lazySequence.sum()
    

This code creates a list eagerly and a sequence lazily, then sums their values.

Identify Repeating Operations

Look at what repeats when processing the numbers.

• Primary operation: Multiplying each number by 2 and summing all numbers.
• How many times: Exactly once for each number from 1 to n.

How Execution Grows With Input

Both eager and lazy methods do the same amount of work for n numbers, but when they do it differs.

Input Size (n)	Approx. Operations
10	About 10 multiplications and 10 additions
100	About 100 multiplications and 100 additions
1000	About 1000 multiplications and 1000 additions

Pattern observation: The total work grows directly with the number of items.

Final Time Complexity

Time Complexity: O(n)

This means the time to complete grows in a straight line as the input size grows.

Common Mistake

[X] Wrong: "Lazy evaluation always makes the program faster."

[OK] Correct: Lazy evaluation delays work but does not reduce the total amount of work needed.

Interview Connect

Understanding how lazy and eager evaluation affect time helps you explain performance choices clearly.

Self-Check

What if we replaced the sequence with a lazy sequence that filters out half the items before mapping? How would the time complexity change?

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