Document ternary operators, closes #14959#14964
Merged
Conversation
josevalim
commented
Nov 27, 2025
| `*` `/` | Left | ||
| `+` `-` | Left | ||
| `++` `--` `+++` `---` `..` `<>` | Right | ||
| `//` (valid only inside `..//`) | Right |
Contributor
There was a problem hiding this comment.
Do we need it here if it is only valid as part of ternary operator?
Member
Author
There was a problem hiding this comment.
Because precedence still applies with operators outside of the ternary.
Contributor
|
Should we also document operator arguments evaluation order? It may not be obvious in case of ternary operators |
Member
Author
Because of macros, argument evaluation order is dependent on how they are implemented, rather than how they are parsed. |
Member
Author
|
💚 💙 💜 💛 ❤️ |
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.
No description provided.