Is it weird to have a non-suspending function that takes a

CoroutineScope

and returns a

Flow

? e.g.,

fun CoroutineScope.getMyStuffs(): Flow<MyStuff>

This is what

Flow.stateIn

does

It's a little weird. What is the scope used for? Why can't you use a scope within the flow collection?

Agreed it’s weird, because this suggests something that could outlive the flow collection Otherwise a scope limited to flow collector would look like

flow { 
  coroutineScope {
  }
}

Or

channelFlow