Improve the Python type hints for basilisp.lang.multifn
#800
Conversation
This file contains hidden or 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
chrisrink10
force-pushed
the
feature/improve-multifn-type-hints
branch
from
a888074 to
fdb2746
Compare
chrisrink10
force-pushed
the
feature/improve-multifn-type-hints
branch
from
fdb2746 to
518714b
Compare
chrisrink10
force-pushed
the
feature/improve-multifn-type-hints
branch
from
518714b to
50ed97f
Compare
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.
Genericthrows an exception when receiving aParamSpecin all versions oftypingbefore Python 3.10, including withtyping_extensions, so this could not be included in #784