Does it make sense to have a `flow` that inside does an `async{}` call? For instance ```flow<Li...

# coroutines

[Pablo]

Does it make sense to have a flow that inside does an async{} call?
For instance

flow<List<Foo>>{
  val list = getFromApi()
  val one = async(<http://Dispatchers.IO|Dispatchers.IO>)
  val two = async(<http://Dispatchers.IO|Dispatchers.IO>)
  val correctList = one.await() + two.await()
  emit(correctList)
}

Or it's better to use async without flow here?
That's pseudo because to do async I need a coroutineScope is there any way to get it from the flow ?

[Erik]

You need a scope to collect the flow. Or a coroutineScope to do the async calls. I would do the latter if it really doesn't need to be a flow.

[Pablo]

means? you wouldn't use flow?

[uli]

async basically does the same thing as an rx single. just simpler. That’s probably why there is no SingleFlow’

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

It would probably be more idiomatic to just make this a suspend function, so that it’s up to the caller whether to wait for it to finish or run concurrently.