Add doc warning about ==> precedence#411
Merged
Merged
Conversation
This was referenced May 6, 2026
jmid
force-pushed
the
implication-doc-warning
branch
from
4ca33f4 to
cd4d6d3
Compare
Collaborator
Author
|
(rebased after having merged #412) |
jmid
force-pushed
the
implication-doc-warning
branch
from
cd4d6d3 to
af0435f
Compare
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
1 participant
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 documentation warnings about how the precedence of
==>interacts badly with the logical connectives&&and||.Fixes #407