This message was deleted.

# coroutines

[Slackbot]

This message was deleted.

[louiscad]

@allan.conda Wrap with coroutineScope { ... }.

[allan.conda]

I tried it, and logged the scope instance.
I get StandaloneCoroutine in the calling fun and DispatchedCoroutine in that one. Ah no, I get this from withContext()
I get ScopeCoroutine with your suggestion.
Is this instance hanging on to the standalone one?

[louiscad]

I don't really understand what you mean, but basically, you need this instead of what you showed:

suspend fun someBatchUpload(): List<Int> = coroutineScope {
    listOf(async { 1 }, async { 2 }).awaitAll()
}

[louiscad]

Also, keep reading the coroutines docs, that'll help you understand it all.

[louiscad]

Since you're doing Android stuff, there's also this page that you'll find useful: https://d.android.com/kotlin/coroutines

[allan.conda]

I don’t really understand what you mean, but basically, you need this instead of what you showed:

Thanks, looks like I’m not making much sense 😄. Actually, I already came to the conclusion that I needed to use coroutineScope exactly like you wrote, because that’s the only one that didn’t throw a warning or error.
But I don’t understand how it works and right now I just assume it does what I think it does; I’m not sure yet how to test scoped coroutine lifecycle so I can’t know for sure.

[louiscad]

There's this great talk about structured concurrency:

https://www.youtube.com/watch?v=Mj5P47F6nJg▾

About lifecycles, it's a different thing, but Android docs should be helfup for that matter after you get stuctured concurrency

[Evan R.]

The android developers video on it is also good. I find that it’s very clear and approachable:

https://youtu.be/ZTDXo0-SKuU▾

[Evan R.]

But at its most basic a coroutineScope is like a standard if statement scope, it’s a code region that doesn’t exit until all the work inside is complete

[Evan R.]

The reason for this is to allow people to run things in parallel but still be able to handle errors and cancel jobs when errors occur

[Evan R.]

If an error is thrown in a parallel job within a coroutine scope, by default the sibling parallel jobs are cancelled and the coroutineScope will rethrow the error that wasn’t dealt with