WIP bpo-43892: Make match patterns explicit in AST #25521
Closed
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
* Separates "pattern" and "expr" nodes in AST * AST node names are derived from the AST proposed in PEP 642, except that MatchValue always matches by equality and a separate MatchConstant node is defined for matching by identity * Grammar definition has been updated to emit the newly defined AST nodes * TODO: update code generator to consume new nodes * TODO: update AST validator to consume new nodes * TODO: update AST unparser to consume new nodes
|
Whoops, didn't mean to create this yet. |
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.
in PEP 642, except that MatchValue always matches
by equality and a separate MatchConstant node is
defined for matching by identity
newly defined AST nodes
https://bugs.python.org/issue43892