Allow IOApp to access the default ExecutionContext
#1457
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Daenyth
force-pushed
the
get-ec
branch
2 times, most recently
from
94e02fa to
ba98993
Compare
What's the correct way to fix that? I'm not super familiar with scaladoc |
|
Easiest way to fix it in the short term is to remove the reference and just use the name. Medium term though we should bring in unidoc or write the references ourselves. |
Currently it's not possible for users of `IOApp` to use the default ExecutionContext that backs the ContextShift. They need to either use `IOApp.WithContext`, or use two unrelated pools, or override the default `ContextShift`. This should remove some needless hoop-jumping, I think Close typelevel#748
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Currently it's not possible for users of
IOAppto use the defaultExecutionContext that backs the ContextShift.
They need to either use
IOApp.WithContext, or use two unrelated pools, oroverride the default
ContextShift.This should remove some needless hoop-jumping, I think
Close #748