You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following test gives a counterexample that does not seem to reproduce in foundry:
function prove_nested_append(uintv, uintw) public {
arr2.push([v,w]);
arr2.push();
arr2.push();
arr2[1].push(arr2[0][0]);
arr2[2].push(w);
// TODO: this is the problematic line!// changing this to arr2[1].push(1), and updating the assertion for the// value of arr2[1][1] to reflect the change makes this test pass...
arr2[1].push(w);
assert(arr2.length==3);
assert(arr2[0].length==2);
assert(arr2[0][0] == v);
assert(arr2[0][1] == w);
assert(arr2[1].length==2);
assert(arr2[1][0] == v);
assert(arr2[1][1] == w);
assert(arr2[2].length==1);
assert(arr2[2][0] == w);
}
This gives me a cex of prove_nested_append(0,2);, but when I try to run that in foundry as a concrete test, I don't trigger any assertions...
The text was updated successfully, but these errors were encountered:
This seems to go into a loop on dc0000163fabe2f128f018ff87ba3f93aefce3d5 during interpretation. Something is a bit weird. Maybe to do with the dual array.
The following test gives a counterexample that does not seem to reproduce in foundry:
This gives me a cex of
prove_nested_append(0,2);
, but when I try to run that in foundry as a concrete test, I don't trigger any assertions...The text was updated successfully, but these errors were encountered: