Skip to content

[Merged by Bors] - fix: update comment and code referring to old split_ifs bug#908

Closed
dwrensha wants to merge 1 commit intomasterfrom
split-ifs-set-value
Closed

[Merged by Bors] - fix: update comment and code referring to old split_ifs bug#908
dwrensha wants to merge 1 commit intomasterfrom
split-ifs-set-value

Conversation

@dwrensha
Copy link
Copy Markdown
Member

@dwrensha dwrensha commented Dec 8, 2022

Now that #761 has landed, we can use split_ifs in the proof of setValue.
The proof is still not as nice as it could be, because we don't have cc yet.

@kim-em
Copy link
Copy Markdown
Contributor

kim-em commented Dec 8, 2022

bors merge

@github-actions github-actions bot added the ready-to-merge This PR has been sent to bors. label Dec 8, 2022
bors bot pushed a commit that referenced this pull request Dec 8, 2022
Now that #761 has landed, we can use `split_ifs` in the proof of `setValue`.
The proof is still not as nice as it could be, because we don't have `cc` yet.
@bors
Copy link
Copy Markdown

bors bot commented Dec 8, 2022

Pull request successfully merged into master.

Build succeeded:

@bors bors bot changed the title fix: update comment and code referring to old split_ifs bug [Merged by Bors] - fix: update comment and code referring to old split_ifs bug Dec 8, 2022
@bors bors bot closed this Dec 8, 2022
@bors bors bot deleted the split-ifs-set-value branch December 8, 2022 05:35
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)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ready-to-merge This PR has been sent to bors.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants