What is a CoroutineDispatcher and when to use IO vs Default?
Tests your grasp of thread pool strategy for CPU vs. I/O-bound tasks. A good answer defines Dispatchers, contrasts the fixed-size Default pool (for CPU work) with the larger IO pool (for blocking I/O), and gives clear examples.
This question tests your understanding of thread pool management, not just coroutine basics. A strong answer defines a CoroutineDispatcher as a context element that directs execution, then contrasts the main dispatchers. Specifically, `Default` has a fixed pool sized to CPU cores for computation, while `IO` has a larger, on-demand pool for blocking I/O operations like network calls or file access. The key red flag is incorrectly suggesting `Dispatchers.IO` is a generic 'background' thread pool for all non-UI tasks.
Read the original → kotlinlang.org
- #coroutines
- #kotlin
- #android
- #concurrency
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.