WithContext for dispatcher switching in Kotlin - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to switch to the IO dispatcher using withContext.

Kotlin

suspend fun fetchData() {
    withContext([1]) {
        // perform IO operation
    }
}

Drag options to blanks, or click blank then click option'

ADispatchers.Main

BDispatchers.Default

CDispatchers.IO

DDispatchers.Unconfined

Attempts:

3 left

💡 Hint

Common Mistakes

Using Dispatchers.Main for IO tasks causes blocking on the main thread.

Using Dispatchers.Default is for CPU-intensive tasks, not IO.

The Dispatchers.IO is used for IO-bound tasks like reading from disk or network calls.

2fill in blank

medium

Complete the code to switch to the Default dispatcher inside withContext.

Kotlin

suspend fun calculate() {
    withContext([1]) {
        // CPU-intensive calculation
    }
}

Drag options to blanks, or click blank then click option'

ADispatchers.Main

BDispatchers.Default

CDispatchers.IO

DDispatchers.Unconfined

Attempts:

3 left

💡 Hint

Common Mistakes

Using Dispatchers.IO for CPU tasks can cause thread starvation.

Using Dispatchers.Main blocks the UI thread.

Dispatchers.Default is used for CPU-intensive tasks like calculations.

3fill in blank

hard

Fix the error in the code by choosing the correct dispatcher for UI updates.

Kotlin

suspend fun updateUI() {
    withContext([1]) {
        // update UI elements
    }
}

Drag options to blanks, or click blank then click option'

ADispatchers.Main

BDispatchers.Unconfined

CDispatchers.IO

DDispatchers.Default

Attempts:

3 left

💡 Hint

Common Mistakes

Using Dispatchers.IO causes UI update crashes.

Using Dispatchers.Default runs UI code off the main thread.

UI updates must happen on the Dispatchers.Main to avoid threading issues.

4fill in blank

hard

Fill both blanks to create a map of words to their lengths, filtering words longer than 4 characters.

Kotlin

val words = listOf("apple", "cat", "banana", "dog")
val lengths = words.associateWith { [1] }
    .filter { it.value [2] 4 }

Drag options to blanks, or click blank then click option'

Ait.length

B>

C<

Dit.count()

Attempts:

3 left

💡 Hint

Common Mistakes

Using < instead of > filters shorter words.

Using it.count() is valid but less common than it.length.

it.length gets the length of each word, and filtering with > 4 keeps words longer than 4 characters.

5fill in blank

hard

Fill all three blanks to create a map of uppercase words to their lengths, filtering lengths greater than 3.

Kotlin

val words = listOf("one", "two", "three", "four")
val result = words.associateBy([1]) { [2] }
    .filter { it.value [3] 3 }

Drag options to blanks, or click blank then click option'

Ait.uppercase()

Bit.length

C>

Dit.lowercase()

Attempts:

3 left

💡 Hint

Common Mistakes

Using lowercase keys instead of uppercase.

Filtering with < instead of >.

We use it.uppercase() as the key, it.length as the value, and filter values greater than 3.

Practice

1. What is the main purpose of withContext in Kotlin coroutines?

easy

A. To switch the coroutine execution to a different dispatcher or thread

B. To create a new coroutine scope

C. To cancel a running coroutine

D. To launch a coroutine on the main thread only

Solution

1. Step 1: Understand what withContext does

   withContext is used to change the dispatcher or thread where a coroutine runs, allowing you to move work to a background thread or back to the main thread.

2. Step 2: Compare options with this purpose

   Only To switch the coroutine execution to a different dispatcher or thread correctly describes switching execution context. Options A, C, and D describe other coroutine features.

3. Final Answer:

   To switch the coroutine execution to a different dispatcher or thread -> Option A

4. Quick Check:

   withContext switches dispatcher = B [OK]

Hint: Remember: withContext changes thread for coroutine code [OK]

Common Mistakes:

• Confusing withContext with launching new coroutines
• Thinking it cancels coroutines
• Assuming it only runs on the main thread

2. Which of the following is the correct syntax to switch to the IO dispatcher using withContext?

easy

A. withContext(Dispatchers.IO()) { /* code */ }

B. withContext(IO.Dispatchers) { /* code */ }

C. withContext(Dispatchers.io) { /* code */ }

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

Solution

1. Step 1: Recall the correct dispatcher name

   The dispatcher for IO operations is Dispatchers.IO with uppercase IO.

2. Step 2: Check syntax correctness

   withContext(Dispatchers.IO) { /* code */ } uses the correct syntax: withContext(Dispatchers.IO) { ... }. Options B and C have wrong casing or order, and A incorrectly uses parentheses after IO.

3. Final Answer:

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

4. Quick Check:

   Correct dispatcher syntax = D [OK]

Hint: Dispatchers.IO is uppercase and no parentheses needed [OK]

Common Mistakes:

• Using lowercase 'io' instead of 'IO'
• Adding parentheses after dispatcher name
• Swapping Dispatchers and IO order

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

import kotlinx.coroutines.*
suspend fun main() = coroutineScope {
    println("Start on: ${'$'}{Thread.currentThread().name}")
    withContext(Dispatchers.Default) {
        println("Inside withContext on: ${'$'}{Thread.currentThread().name}")
    }
    println("End on: ${'$'}{Thread.currentThread().name}")
}

medium

A. Start on: main
Inside withContext on: main
End on: main

B. Start on: DefaultDispatcher-worker-1
Inside withContext on: DefaultDispatcher-worker-1
End on: DefaultDispatcher-worker-1

C. Start on: main
Inside withContext on: DefaultDispatcher-worker-1
End on: main

D. Compilation error due to thread access

Solution

1. Step 1: Identify the starting thread

   The main coroutine starts on the main thread, so the first print shows "main" thread.

2. Step 2: Understand withContext dispatcher switch

   The withContext(Dispatchers.Default) block runs on a background thread named like "DefaultDispatcher-worker-1".

3. Step 3: Check thread after withContext

   After the block, execution returns to the main thread, so the last print shows "main" again.

4. Final Answer:

   Start on: main Inside withContext on: DefaultDispatcher-worker-1 End on: main -> Option C

5. Quick Check:

   withContext switches thread temporarily = C [OK]

Hint: withContext changes thread only inside its block [OK]

Common Mistakes:

• Assuming thread stays switched after withContext
• Thinking withContext runs on main thread always
• Confusing coroutineScope with launch

4. Identify the error in this Kotlin coroutine code using withContext:

fun fetchData() {
    withContext(Dispatchers.IO) {
        println("Fetching data")
    }
}

medium

A. Incorrect dispatcher name, should be Dispatchers.Main

B. Missing suspend modifier on fetchData function

C. withContext cannot be used inside functions

D. No error, code is correct

Solution

1. Step 1: Check usage rules of withContext

   withContext is a suspend function and must be called from a suspend function or coroutine.

2. Step 2: Analyze fetchData function signature

   fetchData is a regular function without suspend, so calling withContext inside it causes a compile error.

3. Final Answer:

   Missing suspend modifier on fetchData function -> Option B

4. Quick Check:

   withContext requires suspend function = A [OK]

Hint: withContext only works inside suspend functions or coroutines [OK]

Common Mistakes:

• Forgetting to mark function as suspend
• Thinking dispatcher name is wrong
• Assuming withContext can be called anywhere

5. You want to perform a heavy computation off the main thread and then update the UI on the main thread. Which code snippet correctly uses withContext to achieve this?

hard

A. suspend fun process() {
withContext(Dispatchers.Default) {
// heavy computation
}
withContext(Dispatchers.Main) {
// update UI
}
}

B. suspend fun process() {
withContext(Dispatchers.Main) {
// heavy computation
}
withContext(Dispatchers.Default) {
// update UI
}
}

C. fun process() {
withContext(Dispatchers.Default) {
// heavy computation
}
withContext(Dispatchers.Main) {
// update UI
}
}

D. suspend fun process() {
withContext(Dispatchers.IO) {
// update UI
}
withContext(Dispatchers.Default) {
// heavy computation
}
}

Solution

1. Step 1: Identify correct dispatcher for heavy computation

   Heavy computation should run on Dispatchers.Default to avoid blocking the main thread.

2. Step 2: Identify correct dispatcher for UI update

   UI updates must happen on Dispatchers.Main to safely interact with the UI.

3. Step 3: Check function signature and order

   The function must be suspend to call withContext. suspend fun process() { withContext(Dispatchers.Default) { // heavy computation } withContext(Dispatchers.Main) { // update UI } } correctly uses suspend and switches dispatchers in the right order.

4. Final Answer:

   suspend fun process() { withContext(Dispatchers.Default) { // heavy computation } withContext(Dispatchers.Main) { // update UI } } -> Option A

5. Quick Check:

   Heavy work on Default, UI on Main = A [OK]

Hint: Heavy work on Default, UI updates on Main dispatcher [OK]

Common Mistakes:

• Running heavy work on Main thread
• Updating UI off the Main thread
• Not marking function as suspend