I keep making this mistake:

CoroutineScope.launch {
    stateFlowA.collect {
        foo()
    }
    stateFlowB.collect {
        bar()
    }
}

And wondering why bar() isn't called. (It's because stateFlowA never completes, as it's a StateFlow). I think I'm just tempted to declare both suspend functions inside the one

CoroutineScope.launch { }

block out of convenience. Anyway, the simple solution is to just not make this mistake. But I wonder if I'm doing this because there's a problem with my mental model. I think maybe this comes about because

launch{}

is the only operator I ever use to kick-off a suspend fun (I rarely consider

async

, and I'm not sure if there are others. I don't have a specific question, just wanted to discuss this and see if anyone else has the same problem. I'm hoping the discussion will help correct my mental model.

I would say that almost in all cases you shouldn’t use collect for such cases and instead use onEach().launchIn(scope)

Oh yeah, that's a little nicer, and definitely helps avoid this mistake