Clarify operator precedence in declaration check - #731
Merged
Conversation
Fixes a bug where mixing bitwise `&` and logical `&&` without explicit parentheses caused incorrect operator precedence during XML header validation.
Owner
|
What is the bug? |
Contributor
Author
|
Add explicit parentheses around the bitwise-AND group to clarify operator precedence and avoid compiler warnings when building with -Werror. |
Owner
|
What compiler are you using that gives the warning, with what options? Neither GCC nor Clang seem to warn on this with |
zeux
changed the title
Owner
|
Going to merge this a little later today as cleanup. |
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
2 participants
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.
Fixes a bug where mixing bitwise
&and logical&&without explicit parentheses caused incorrect operator precedence during XML header validation.