[Merged by Bors] - fix: add parens so that sequences works as expected in setValue#914
Closed
[Merged by Bors] - fix: add parens so that sequences works as expected in setValue#914
Conversation
Contributor
|
bors merge |
bors bot
pushed a commit
that referenced
this pull request
Dec 12, 2022
Followup to #908. Apparently `<;>` (in addition to plain `;`) has higher precedence than `try`. Adding parentheses restores the expected behavior. This isn't the first time we've been tripped up by unexpected precedence in the sequencing operators. See e.g. #370 (comment)
|
Pull request successfully merged into master. Build succeeded:
|
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.
Followup to #908.
Apparently
<;>(in addition to plain;) has higher precedence thantry.Adding parentheses restores the expected behavior.
This isn't the first time we've been tripped up by unexpected precedence in the sequencing operators. See e.g. #370 (comment)