Also, in what situation is a `CoroutineScope` not ...

# coroutines

[nwh]

Also, in what situation is a CoroutineScope not used for what is essentially an on-going Job with a lifecycle? That's how I've always thought about it (I believe it was mentioned in a kotlinconf talk)

[Zach Klippenstein (he/him) [MOD]]

A CoroutineScope is just something that provides a CoroutineContext. That context can contain whatever you want – the dispatcher to use, uncaught exception handlers, a name for debugging, etc.