Can anyone explain why the `doSomething()` in this snippet prevents the outer `run()` loop from cont...

# coroutines

[Sam Garfinkel]

Can anyone explain why the doSomething() in this snippet prevents the outer run() loop from continuing? You’ll notice that "Continuing to run" is printed after "doSomething with $hello done" which is the opposite pattern I’m looking for.

broken.kt

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

doSomething uses coroutineScope, which won't return until all its child coroutines have completed.

[Sam Garfinkel]

Is there an alternative function I’m looking for here?

[Sam Garfinkel]

So in other words, to parallelize and loop, I need to move coroutineScope into the outer run()?

[octylFractal]

if you want to immediately launch, remove suspend and coroutineScope and make it an extension on CoroutineScope instead

[octylFractal]

yes, you want it outside of the loop

[octylFractal]

in the case of parallelism, I'd leave the inner part as suspend and just call it inside async {} (or launch if you don't need results)

[Sam Garfinkel]

Makes sense, thanks.

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

This is purely a matter of style, but in this case I would probably pass the scope in as a regular param instead of a receiver, and name the function doSomethingIn. Receiver feels odd to me unless the function is a generic launcher or something, and this convention reads really clearly that this function will launch a coroutine in a given scope. But same idea regardless.

[Sam Garfinkel]

@Zach Klippenstein (he/him) [MOD] Agree completely, this was a sanitized toy example of the problem. The actual code follows better code styles