Lazy evaluation means waiting to do work until it's really needed. Eager evaluation means doing work right away. This helps save time and resources or get results quickly.
Lazy evaluation vs eager evaluation in Kotlin
val eagerValue = compute() val lazyValue by lazy { compute() }
eagerValue runs compute() immediately.
lazyValue runs compute() only when first used.
val eager = "Hello".uppercase() println(eager)
lazyValue is used the first time. The message prints only once.val lazyValue by lazy { println("Computing now...") "Hello".uppercase() } println("Before using lazyValue") println(lazyValue) println(lazyValue)
This program shows the difference. The eager value is computed right away. The lazy value waits until it is printed the first time. The compute function prints a message when it runs, so you can see when it happens.
fun compute(): String { println("Computing the value...") return "Kotlin" } fun main() { val eagerValue = compute() // runs immediately println("Eager value: $eagerValue") val lazyValue by lazy { compute() } // runs only when used println("Before accessing lazyValue") println("Lazy value: $lazyValue") println("Accessing lazyValue again: $lazyValue") }
Lazy evaluation runs the code only once, then remembers the result.
Eager evaluation runs the code immediately, even if the result is never used.
Use lazy evaluation to save resources when the result might not be needed.
Lazy evaluation delays work until needed, eager evaluation does it right away.
Kotlin's by lazy helps create lazy values easily.
Choosing between lazy and eager depends on when you want your code to run.
Practice
Solution
Step 1: Understand lazy evaluation
Lazy evaluation means the program waits to calculate a value until it is actually needed.Step 2: Understand eager evaluation
Eager evaluation means the program calculates the value right away when the code runs.Final Answer:
Lazy evaluation delays computation until the value is needed, eager evaluation computes immediately. -> Option CQuick Check:
Lazy = delay, Eager = immediate [OK]
- Confusing which evaluation runs first
- Thinking lazy evaluation runs immediately
- Assuming eager evaluation delays work
Solution
Step 1: Recall Kotlin lazy syntax
Kotlin usesval x by lazy { ... }to declare lazy properties.Step 2: Check each option
val x by lazy { 10 } matches the correct syntax. The other options are incorrect Kotlin syntax.Final Answer:
val x by lazy { 10 } -> Option AQuick Check:
Use 'by lazy { }' for lazy properties [OK]
- Using 'lazy val' instead of 'val by lazy'
- Assigning lazy without 'by'
- Placing 'by lazy' after the value
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)
}Solution
Step 1: Understand eager initialization
The variableeagerusesalso, so "Eager initialized" prints immediately when declared.Step 2: Understand lazy initialization and main flow
Lazy variablelazyValprints "Lazy initialized" only when first accessed. The main prints "Start main", then printseager(already initialized), then accesseslazyValtwice. The first access triggers initialization print, second does not.Final Answer:
Eager initialized Start main Eager Lazy initialized Lazy Lazy -> Option BQuick Check:
Eager prints first, lazy prints on first access [OK]
- Assuming lazy prints before main
- Thinking lazy prints every access
- Mixing order of prints
val lazyValue by lazy {
println("Calculating...")
42
}
fun main() {
println(lazyValue)
lazyValue = 50
}Solution
Step 1: Check property mutability
The propertylazyValueis declared withval, meaning it cannot be reassigned after initialization.Step 2: Analyze reassignment in main
The code tries to assignlazyValue = 50, which is illegal for avalproperty and causes a compilation error.Final Answer:
Cannot reassign a val property declared with 'by lazy'. -> Option AQuick Check:
val lazy properties are read-only, no reassignment [OK]
- Trying to assign a new value to a val lazy property
- Confusing val with var for lazy properties
- Thinking lazy block must return String
Solution
Step 1: Understand lazy loading benefit
Loading a large config only when needed saves startup time and resources.Step 2: Choose lazy evaluation syntax
Usingval config by lazy { loadConfig() }delays loading until first use, improving performance.Final Answer:
Declare the configuration as val config by lazy { loadConfig() } so it loads only on first access. -> Option DQuick Check:
Lazy loading delays heavy work until needed [OK]
- Loading config immediately even if not needed
- Using var without lazy, causing unnecessary loads
- Loading config repeatedly inside functions
Ready to prove it?
Pass the test and this pattern moves unknown
