Hey, hope this isn't too annoying!

# announcements

[Ani Mehta]

Hey, hope this isn't too annoying!

[mon]

Not too sure, but maybe something like this:

Untitled

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

Try not to use GlobalScope if at all possible. Usually there is some concept of “lifetime” that surrounds where you’re launching coroutines from, so you can create a CoroutineScope that represents that. Other than that, Mon’s solution is probably what I’d do.

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

And come join us in #C1CFAFJSK!

[Ani Mehta]

Thanks both!

What I have done for now is

val responses = needsResponses.map {
        GlobalScope.async {
            // get response
        }
    }

    responses.map { it.await() }.map {
        // process response
    }

[Ani Mehta]

Will look into creating a coroutine scope. Any particular disadvantages of using GlobalScope? There's no chance of this workflow overlapping with another instance of it

[Ani Mehta]

Actually, rewrote to something more similar to Mon's solution, thanks!

needsResponses
        .map {
            GlobalScope.async {
                // get responses
            }
        }
        .awaitAll()
        .forEach {
            // process responses
        }

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

GlobalScope lets you leak coroutines. It also makes it easier to refactor code without it being in the correct scope in its new location.

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

Also see this article: https://medium.com/@elizarov/the-reason-to-avoid-globalscope-835337445abc

[ken]

How do u like Kotlin so far compared to Golang @Ani Mehta