In `coroutineScope`, a failure in one child cancels the whole scope (and other children). In `supervisorScope`, child failures don’t cancel siblings; only the failing child is cancelled. Use supervisorScope when you want isolation between children.
Advanced answer
Deep dive
Expanding on the short answer — what usually matters in practice:
Explain the "why", not just the "what" (intuition + consequences).
Trade-offs: what you gain/lose (time, memory, complexity, risk).
Edge cases: empty inputs, large inputs, invalid inputs, concurrency.
Examples
A tiny example (an explanation template):
// Example: discuss trade-offs for "coroutinescope-vs-supervisorscope:-how-do-they-h"
function explain() {
// Start from the core idea:
// In `coroutineScope`, a failure in one child cancels the whole scope (and other children).
}
Common pitfalls
Too generic: no concrete trade-offs or examples.
Mixing average-case and worst-case (e.g., complexity).