Fix SQL Server operator precedence table #33875
Merged
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
Specifically, binary logical operators have the same precedence as `+`/`-`. The table is now aligned with the referenced document, plus shift operators. They seem to have the same precedence as `+`/`-` according to manual tests; no documentation about this is available. Fixes dotnet#30248.
|
I was wondering if there is a reasonable approach to testing that the precedence table is correct, but so far I have not found a "general" approach. |
roji
approved these changes
Jun 2, 2024
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.
Specifically, binary logical operators have the same precedence as
+/-.The table is now aligned with the referenced document, plus shift operators.
They seem to have the same precedence as
+/-according to manual tests; no documentation about this is available.Fixes #30248.