parse.py + parse_test.py type fixes #90
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
These are required to avoid "no-untyped-call" when invoking those constructors in `parse.py`.
This is sufficient to allow `mypy --strict greenery/parse{,_test}.py`
rwe
changed the title
qntm
approved these changes
Mar 16, 2023
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.
This makes the result types consistent in matcher helpers in
parse.py, defines a genericMatchResult[…]type, and annotates the functions there.This is sufficient to pass
mypy --strict greenery/parse{,_test}.py.One change was required in
rxelems, to avoiduntyped-callerrors due to missing annotations on theConcandPatternconstructors: that change is also included effectively in #89 and should merge cleanly.