docs: clarify mixed comparison/equality operators#9862
Merged
orizi merged 1 commit intostarkware-libs:mainfrom Apr 21, 2026
Merged
Conversation
orizi
approved these changes
Apr 21, 2026
Collaborator
orizi
left a comment
There was a problem hiding this comment.
@orizi reviewed 1 file and all commit messages, and made 1 comment.
Reviewable status:complete! all files reviewed, all discussions resolved (waiting on Elena343-ai).
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
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.
Summary
Document that mixed consecutive comparison/equality operators such as
a < b == canda == b < care also unsupported on the comparison operators page, and show the supported conjunction/parenthesized alternatives.Type of change
Why is this change needed?
The comparison operators page currently explains that
a < b < cis unsupported, but it does not mention that mixed consecutive comparison/equality operators are rejected as well. Because the same page also says that comparison and equality operators share a precedence level, readers can reasonably infer that forms likea < b == care valid. The parser rejects these expressions withE1028.What was the behavior or documentation before?
The page only documented unsupported chained comparisons such as
a < b < c.What is the behavior or documentation after?
The page also documents unsupported mixed forms such as
a < b == canda == b < c, andshows explicit conjunction/parenthesized alternatives.
Related issue or discussion (if any)
N/A
Additional context