Fix an explanation of flowOn Operator #4402
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In this part, it says :
Otherwise, if changing dispatcher is required, it collects flow emissions in one coroutine that is run using a specified [context] and emits them from another coroutines with the original collector's context
and this explanation is reversed.
If flowOn passes CoroutineDispatcher, then the flow's emissions are performed in a coroutine running with the specified CoroutineContext not collector's context. The collector's original context is used to collect values emitted from the flow.
You can easily configure this by running below code.
The result of code is:
The new coroutine(coroutine#2) is using DefaultDispatcher-worker-1 of Dispatchers.IO. And runBlocking Coroutine(coroutine#1) is collecting the value.