Update docs about creating custom CoroutineScopes #3306
Conversation
| * * `CoroutineScope()` uses [Dispatchers.Default] for its coroutines. | ||
| * * `MainScope()` uses [Dispatchers.Main] for its coroutines. | ||
| * * `CoroutineScope()` uses the [context][CoroutineContext] provided to it as a parameter for its coroutines | ||
| * and adds a [Job] if one is not provided as part of the context. |
There was a problem hiding this comment.
The part about Dispatchers.Default is important though. If one knows that Dispatchers.Default is used by default, yes, it's obvious what happens when a dispatcher is not specified, but if one does not, it's unclear where to look.
There was a problem hiding this comment.
Every coroutine builder mentions Dispatchers.Default though:
If the context does not have any dispatcher or other [ContinuationInterceptor], then [Dispatchers.Default] is used.
The parent job is inherited from the [CoroutineScope] as well, but it can also be overridden
with a corresponding [context] element.
And mentioning Dispatchers.Default here is just being incorrect -- CoroutineScope() does not provide any dispatcher and each coroutine decides what to use on its own. E.g. some may use Dispatches.Unconfined when the dispatcher is not supplied
There was a problem hiding this comment.
Ah, ok, didn't notice launch mentioning Dispatchers.Default.
3 participants
Clarify the difference between
MainScope()andCoroutineScope(), remove mention ofCustomScope