Flow context preservation in Kotlin - Step-by-Step Execution

Concept Flow - Flow context preservation

Start Flow

↓

Emit values

↓

Flow collects values

↓

Preserve Coroutine Context

↓

Process values with context

↓

Flow completes

This flow shows how a Kotlin Flow emits values, collects them, and preserves the coroutine context during processing.

Execution Sample

Kotlin

val flow = flow {
  emit(1)
  emit(2)
}

flow.collect { value ->
  println("Collected $value")
}

This code creates a flow that emits two values and collects them, printing each collected value.

Execution Table

Step	Action	Coroutine Context	Value Emitted	Value Collected	Output
1	Start flow builder	Main	None	None	None
2	Emit value 1	Main	1	None	None
3	Collect value 1	Main	1	1	Collected 1
4	Emit value 2	Main	2	None	None
5	Collect value 2	Main	2	2	Collected 2
6	Flow completes	Main	None	2	Collected 2

💡 Flow completes after emitting and collecting all values preserving the coroutine context.

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	After Step 5	Final
value	None	1	1	2	2	2
coroutineContext	Main	Main	Main	Main	Main	Main

Key Moments - 2 Insights

Why does the coroutine context remain 'Main' during emission and collection?

Because the flow preserves the coroutine context from the collector side, as shown in execution_table steps 2 to 5, the context stays 'Main' throughout.

What happens if the flow emits values but the collector is on a different context?

The flow switches to the collector's coroutine context when collecting values, preserving context consistency as seen in the flow's design.

Visual Quiz - 3 Questions

Look at the execution table, what is the value collected at step 3?

A None

B 1

C 2

D 0

💡 Hint

Check the 'Value Collected' column at step 3 in the execution_table.

At which step does the flow emit the value 2?

A Step 4

B Step 2

C Step 3

D Step 5

💡 Hint

Look at the 'Value Emitted' column in the execution_table.

If the coroutine context changed to 'IO' during collection, what would change in the execution table?

A The 'Value Emitted' would change to 'IO'.

B The 'Output' would be empty.

C The 'Coroutine Context' column would show 'IO' during collection steps.

D The flow would emit no values.

💡 Hint

Focus on the 'Coroutine Context' column in the execution_table during collection steps.

Concept Snapshot

Kotlin Flow preserves coroutine context during emission and collection.
Flow emits values asynchronously.
Collector processes values in its coroutine context.
Context preservation ensures consistent execution environment.
Use flow { emit(...) } and collect { } to handle streams safely.

Full Transcript

This example shows a Kotlin Flow emitting two values and collecting them while preserving the coroutine context. The flow starts in the 'Main' context, emits values 1 and 2, and the collector receives these values also in the 'Main' context. The coroutine context remains consistent throughout emission and collection, ensuring safe and predictable asynchronous processing. The execution table traces each step, showing the emitted and collected values and the context state. Key moments clarify why context preservation matters and what happens if contexts differ. The visual quiz tests understanding of values and context at each step.