Fix Cats Effect IO type inference #2459
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.
As mention in this comment the generalisation of implicits to provide
Executor
/Functor
typeclass instances for all types withAsync
/CatsFunctor
instances losesIO
specificity and implicit precedence priority, making client execution infer to the defaultFuture
effect return type. This makes using theIO
effect type very unwieldy, having to explicitly state all type parameters for client execution.This PR brings back
IO
type inference without losing support for otherAsync
effect type.