Coroutine context and dispatchers in Kotlin - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a Coroutine Context in Kotlin?

A Coroutine Context is a set of elements that define the behavior of a coroutine, such as its job, dispatcher, and other metadata. It controls how and where the coroutine runs.

beginner

What role does a Dispatcher play in Kotlin coroutines?

A Dispatcher decides the thread or thread pool on which the coroutine runs. It controls the execution environment, like running on the main thread, IO thread, or a background thread pool.

intermediate

Name the four standard dispatchers provided by Kotlin coroutines.

The four standard dispatchers are:
1. Dispatchers.Main - runs on the main UI thread
2. Dispatchers.IO - optimized for IO tasks
3. Dispatchers.Default - for CPU-intensive work
4. Dispatchers.Unconfined - starts coroutine in the current thread but can resume in another

intermediate

How can you combine multiple elements in a Coroutine Context?

You can combine elements using the + operator. For example, Dispatchers.IO + Job() combines a dispatcher with a job to form a complete context.

intermediate

What happens if you launch a coroutine without specifying a dispatcher?

If no dispatcher is specified, the coroutine inherits the dispatcher from its parent coroutine context. If there is no parent, it uses Dispatchers.Default by default.

Which dispatcher should you use for network or disk operations in Kotlin coroutines?

A Dispatchers.Default

B Dispatchers.Main

C Dispatchers.IO

D Dispatchers.Unconfined

Dispatchers.IO is optimized for blocking IO tasks like network or disk operations.

What does Dispatchers.Main do?

A Runs coroutines on a background thread pool

B Runs coroutines on the main UI thread

C Runs coroutines without any thread confinement

D Runs coroutines on the IO thread pool

Dispatchers.Main runs coroutines on the main UI thread, suitable for updating UI.

How do you combine a Job and a Dispatcher in a coroutine context?

A Using the | operator

B Using the & operator

C Using the * operator

D Using the + operator

The + operator combines multiple elements into a single coroutine context.

What is the default dispatcher if none is specified and no parent context exists?

A Dispatchers.Default

B Dispatchers.Main

C Dispatchers.IO

D Dispatchers.Unconfined

Dispatchers.Default is used by default for coroutines without a specified dispatcher or parent.

Which dispatcher starts coroutine in the current thread but can resume in another thread?

A Dispatchers.Unconfined

B Dispatchers.Main

C Dispatchers.IO

D Dispatchers.Default

Dispatchers.Unconfined starts in the current thread but can resume in a different thread later.

Explain what a coroutine context is and why dispatchers are important in Kotlin coroutines.

Think about how coroutines know where and how to run.

List and describe the four main dispatchers in Kotlin coroutines and when to use each.

Consider UI updates, IO tasks, CPU work, and thread flexibility.

Practice

1. Which dispatcher should you use in Kotlin coroutines to perform heavy CPU-intensive tasks?

easy

A. Dispatchers.Default

B. Dispatchers.IO

C. Dispatchers.Main

D. Dispatchers.Unconfined

Solution

1. Step 1: Understand dispatcher roles

   Dispatchers.Default is designed for CPU-intensive work like calculations.

2. Step 2: Match task type to dispatcher

   Heavy CPU tasks should use Dispatchers.Default to avoid blocking UI or IO threads.

3. Final Answer:

   Dispatchers.Default -> Option A

4. Quick Check:

   CPU work = Dispatchers.Default [OK]

Hint: Use Default for CPU tasks, IO for disk/network, Main for UI [OK]

Common Mistakes:

• Using Dispatchers.IO for CPU tasks
• Using Dispatchers.Main for background work
• Confusing Dispatchers.Unconfined with Default

2. Which of the following is the correct syntax to launch a coroutine on the IO dispatcher in Kotlin?

easy

A. launch(Dispatchers.Background) { /* code */ }

B. launch(Dispatchers.Default) { /* code */ }

C. launch(Dispatchers.Main) { /* code */ }

D. launch(Dispatchers.IO) { /* code */ }

Solution

1. Step 1: Identify correct dispatcher name

   Dispatchers.IO is the correct dispatcher for IO tasks.

2. Step 2: Check syntax correctness

   launch(Dispatchers.IO) { /* code */ } is valid Kotlin coroutine syntax.

3. Final Answer:

   launch(Dispatchers.IO) { /* code */ } -> Option D

4. Quick Check:

   IO dispatcher syntax = launch(Dispatchers.IO) { /* code */ } [OK]

Hint: Use Dispatchers.IO exactly as shown to launch IO coroutines [OK]

Common Mistakes:

• Using non-existent Dispatchers.Background
• Mixing up Dispatchers.Default and Dispatchers.IO
• Forgetting braces or parentheses

3. What will be the output of this Kotlin coroutine code snippet?

import kotlinx.coroutines.*

fun main() = runBlocking {
    launch(Dispatchers.Default) {
        println("Running on: " + Thread.currentThread().name)
    }.join()
}

medium

A. Running on: DefaultDispatcher-worker-1

B. Running on: main

C. Running on: IO-thread-1

D. Running on: Unconfined

Solution

1. Step 1: Identify dispatcher thread naming

   Dispatchers.Default uses a shared pool named like DefaultDispatcher-worker-n.

2. Step 2: Check printed thread name

   The coroutine runs on a background thread named DefaultDispatcher-worker-1 or similar.

3. Final Answer:

   Running on: DefaultDispatcher-worker-1 -> Option A

4. Quick Check:

   Default dispatcher thread name = Running on: DefaultDispatcher-worker-1 [OK]

Hint: Default dispatcher runs on worker threads, not main [OK]

Common Mistakes:

• Assuming it runs on main thread
• Confusing IO dispatcher thread names
• Expecting Unconfined dispatcher output

4. Identify the error in this Kotlin coroutine code snippet:

fun main() = runBlocking {
    launch(Dispatchers.Main) {
        println("Hello from Main")
    }
}

medium

A. println is not allowed inside coroutines

B. Dispatchers.Main cannot be used in runBlocking without a UI environment

C. launch must be called with Dispatchers.Default

D. Missing join() call on launched coroutine

Solution

1. Step 1: Understand Dispatchers.Main requirements

   Dispatchers.Main requires a UI thread environment (like Android or JavaFX).

2. Step 2: Check runBlocking context

   runBlocking runs on the main thread but usually outside UI context, so Dispatchers.Main is invalid here.

3. Final Answer:

   Dispatchers.Main cannot be used in runBlocking without a UI environment -> Option B

4. Quick Check:

   Main dispatcher needs UI thread = Dispatchers.Main cannot be used in runBlocking without a UI environment [OK]

Hint: Use Dispatchers.Main only in UI apps with proper environment [OK]

Common Mistakes:

• Assuming Dispatchers.Main works everywhere
• Forgetting to join coroutine before main ends
• Thinking println is disallowed in coroutines

5. You want to perform a network request in a Kotlin coroutine and then update the UI with the result. Which dispatcher combination should you use to ensure correct threading?

hard

A. launch(Dispatchers.Default) { val data = fetchData(); updateUI(data) }

B. launch(Dispatchers.Main) { val data = fetchData(); updateUI(data) }

C. launch(Dispatchers.IO) { val data = fetchData(); withContext(Dispatchers.Main) { updateUI(data) } }

D. launch(Dispatchers.IO) { val data = fetchData(); updateUI(data) }

Solution

1. Step 1: Identify correct dispatcher for network request

   Network requests should run on Dispatchers.IO to avoid blocking the main thread.

2. Step 2: Switch to Main dispatcher for UI update

   UI updates must happen on Dispatchers.Main to safely update UI components.

3. Step 3: Analyze code structure

   launch(Dispatchers.IO) { val data = fetchData(); withContext(Dispatchers.Main) { updateUI(data) } } correctly uses Dispatchers.IO for fetching and withContext(Dispatchers.Main) for UI update.

4. Final Answer:

   launch(Dispatchers.IO) { val data = fetchData(); withContext(Dispatchers.Main) { updateUI(data) } } -> Option C

5. Quick Check:

   IO for network + Main for UI = launch(Dispatchers.IO) { val data = fetchData(); withContext(Dispatchers.Main) { updateUI(data) } } [OK]

Hint: Use IO for background, switch to Main for UI updates [OK]

Common Mistakes:

• Updating UI on IO or Default dispatcher
• Running network request on Main dispatcher
• Not switching context before UI update