I've come with yet another

coroutineScope

vs

withContext

question. Does

coroutineScope

change the

coroutineContext

like

withContext

does? (I'm referring to the intrinsic

coroutineContext

and not

CoroutineScope.coroutineContext

). The docs aren't explicit enough to inspire confidence.

Yes, because

coroutineContext

function creates a new coroutine with own Job (same as withContext actually)

So

flow { coroutineScope { emit(...) } }

will not work then?

why?

flow { coroutineScope { emit(....) } }

is allowed. Even though

coroutinesScope { ... }

creates a new job and a new context with it, it is considered an continuation of its parent context that runs sequentially with it. This is specifically allowed to make it possible to write:

flow { 
    coroutineScope {
          // can launch concurrent stuff here
         launch { ... }
         // but can only emit sequentially from here
         emit(...) 
    }
}