Include runBlocking()
in context and dispatchers tutorial code
#3674
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.
The texts in the "Dispatchers and threads" and "Unconfined vs confined dispatcher" sections explicitly mention the example code having
runBlocking
call somewhere but the sample code does not show the call. Because of that the reader hass to assume (or check the source code) where therunBlocking
call happens.I'd propose to include the call to
runBlocking
in the code samples, so that the readers don't have to guess where the actualrunBlocking
call is done.