<@U21LBQBU2> you don’t need an extra `coroutineSco...
# coroutines
e
@bj0 you don’t need an extra
coroutineScope
. The
launch
already provides one.
b
Oh ok, I wasn't sure if the global
launch
waited for the inner `launch`es to complete or not
e
Every function that provides
CoroutineScope
is consistent in that it is waiting. The only exception is
currentScope
(and it might be a good resource to deprecate it)
b
Ok, all that makes sense, but if all the builders include a
CoroutineScope
, what's the use-case of
coroutineScope
builder? I'm struggling to think of where I would use it instead of the current scope