-
Notifications
You must be signed in to change notification settings - Fork 6.1k
test: indexed (compound) assignment evaluation order and single-evaluation #16756
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
msooseth
wants to merge
4
commits into
argotorg:develop
Choose a base branch
from
msooseth:test-compound-assignment-lhs-side-effect
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
30 changes: 30 additions & 0 deletions
30
...solidity/semanticTests/operators/compound_assignment_evaluation_order_and_single_eval.sol
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,30 @@ | ||
| // Pins down evaluation order and single-evaluation for indexed | ||
| // (compound) assignment: | ||
| // - In `a[f()] = g()`, the RHS `g()` is evaluated before the LHS | ||
| // index `f()`, so RHS side effects are observable when the index | ||
| // is computed. | ||
| // - In `a[f()] += v`, the LHS index `f()` is evaluated exactly once; | ||
| // the slot computation is not re-evaluated for the write side. | ||
| contract C { | ||
| uint[2] public a; | ||
| uint public counter; | ||
|
|
||
| function bumpIdx() internal returns (uint) { | ||
| counter += 1; | ||
| return counter - 1; | ||
| } | ||
|
|
||
| function calculateVal() internal returns (uint) { | ||
| return 10 * (counter + 100); | ||
| } | ||
|
|
||
| function run() public returns (uint c, uint a0, uint a1) { | ||
| a[bumpIdx()] = calculateVal(); | ||
| a[bumpIdx()] = calculateVal(); | ||
| c = counter; | ||
| a0 = a[0]; | ||
| a1 = a[1]; | ||
| } | ||
| } | ||
| // ---- | ||
| // run() -> 2, 1000, 1010 |
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Naming:
ir_lvalue_compound_assignment.sol->compound_assignment_evaluation_order_and_single_eval.sol. It does nLet's also put it in
operators/. Or create a separate dir for evaluation order. ThisviaYul/dir is a legacy thing and we should get rid of it, moving tests to more relevant locations, not add more. I'm not even sure why they were singled out in the first place (most of them don't seem particularly IR-specific). Now it just makes it harder to check if we have a test for something already.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't know. I have moved it now :)