Terminal operations trigger execution in Kotlin - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ query_result

intermediate

What is the output of this Kotlin sequence operation?

Consider the following Kotlin code using sequences. What will be printed when the code runs?

Kotlin

val numbers = sequenceOf(1, 2, 3, 4, 5)
val result = numbers
    .map {
        println("Mapping $it")
        it * 2
    }
    .filter {
        println("Filtering $it")
        it > 5
    }
println("Before terminal operation")
val output = result.toList()
println("Output: $output")

A

Before terminal operation
Mapping 1
Mapping 2
Filtering 2
Mapping 3
Filtering 4
Mapping 4
Filtering 6
Mapping 5
Filtering 8
Filtering 10
Output: [6, 8, 10]

B

Mapping 1
Mapping 2
Mapping 3
Mapping 4
Mapping 5
Filtering 2
Filtering 4
Filtering 6
Filtering 8
Filtering 10
Before terminal operation
Output: [6, 8, 10]

C

Before terminal operation
Mapping 1
Filtering 2
Mapping 2
Filtering 4
Mapping 3
Filtering 6
Mapping 4
Filtering 8
Mapping 5
Filtering 10
Output: [6, 8, 10]

D

Before terminal operation
Output: []

💡 Hint

Remember that sequences in Kotlin are lazy and only execute when a terminal operation is called.

The println("Before terminal operation") runs before any mapping or filtering because sequences are lazy. The mapping and filtering print statements run only when toList() is called, triggering the terminal operation and causing the sequence to execute.

🧠 Conceptual

intermediate

Why do terminal operations trigger execution in Kotlin sequences?

In Kotlin, why do terminal operations like toList() or count() cause the sequence to execute, while intermediate operations like map() or filter() do not?

A Because intermediate operations only build a processing pipeline without processing elements, and terminal operations start the actual processing.

B Because intermediate operations are executed immediately, but terminal operations delay execution until needed.

C Because terminal operations cache the results, while intermediate operations discard them.

D Because Kotlin sequences do not support intermediate operations without terminal operations.

💡 Hint

Think about lazy evaluation and how sequences process elements.

Intermediate operations on sequences are lazy and only build a chain of operations. The actual processing happens only when a terminal operation is called, which triggers the execution of the entire chain.

📝 Syntax

advanced

Which Kotlin code snippet correctly triggers execution of a sequence?

Given a Kotlin sequence, which of the following code snippets correctly triggers its execution?

A

val seq = sequenceOf(1, 2, 3).map { it * 2 }
seq.forEach { it }

B

val seq = sequenceOf(1, 2, 3).map { it * 2 }
// No terminal operation here

C

val seq = sequenceOf(1, 2, 3).map { it * 2 }
println(seq)

D val seq = sequenceOf(1, 2, 3).map { it * 2 }.toList()

💡 Hint

Which operation forces the sequence to process its elements?

Only terminal operations like toList() or forEach() trigger execution. Just printing the sequence or defining it does not execute the pipeline.

🔧 Debug

advanced

Why does this Kotlin sequence code print nothing?

Analyze the following Kotlin code. Why does it print nothing?

Kotlin

val seq = sequenceOf(1, 2, 3, 4)
seq.map {
    println("Processing $it")
    it * 10
}

A Because the println statement is inside map and map does not execute at all.

B Because map is an intermediate operation and no terminal operation is called to trigger execution.

C Because sequenceOf creates an empty sequence by default.

D Because the map operation returns a list, but it is not printed.

💡 Hint

Think about when sequences actually run their operations.

Intermediate operations like map are lazy and do not execute until a terminal operation is called. Since no terminal operation is called, the println inside map never runs.

❓ optimization

expert

How to optimize Kotlin sequence processing to avoid unnecessary computations?

Given a Kotlin sequence with multiple intermediate operations, which approach optimizes execution by avoiding processing elements unnecessarily?

A Use terminal operations like first() or find() to stop processing early when a condition is met.

B Call toList() after every intermediate operation to force execution step-by-step.

C Avoid terminal operations to keep the sequence lazy and never execute it.

D Use map() to transform all elements before filtering them with filter().

💡 Hint

Think about how terminal operations can stop processing early.

Terminal operations like first() or find() stop processing as soon as the result is found, avoiding unnecessary work. Calling toList() repeatedly forces full execution multiple times, which is inefficient.