more unicode dotty operators #26262
Merged
more unicode dotty operators #26262
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
stevengj
added
kind:breaking
|
CI failure on Win32 is #26255. Not sure what the Win64 failure is — I'm not seeing the error message in the log? |
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 PR adds the Unicode characters
… ⁝ ⋮ ⋱ ⋰ ⋯as binary operators with the same precedence as:and... (Fixes #24269.) Breaking because⋮ ⋱ ⋰ ⋯were formerly parsed as identifiers.It also changes
≔ ⩴ ≕from comparison precedence to assignment precedence, since colon-equals is an assignment by convention (and we already parse:=with assignment precedence). Also breaking.I doubt that this affects any extant code.
In the future, we may want to also accept
⫶(U+2af6) and/or︙(U+fe19) as synonyms for⁝(U+205d) or⋮(U+22ee), but #25157 needs to be fixed before we can canonicalize operators. That won't be a breaking change since⫶ ︙are not currently valid in identifiers.