Make subtyping in uncurried mode work past type definitions. #6086
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
cristianoc
force-pushed
the
subtype_uncurried
branch
from
f9a66e8
to
371a244
Compare
cristianoc
changed the title
Subtyping from uncurried to curried functions was not working when the expected curried function was under a type definition. This would give type errors on components that take a component type as prop.
cristianoc
force-pushed
the
subtype_uncurried
branch
from
371a244
to
cbb2405
Compare
4 tasks
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.
Subtyping from uncurried to curried functions was not working when the expected curried function was under a type definition. This would give type errors on components that take a component type as prop.