Open jspam opened 12 years ago
How can you close this issue when the test I wrote for it still fails? This time it is because you didn’t set the type of the _return
variable declaration (which, I think, should be the same type as the function’s return type)
Because the test fails also because the prover doesn't use the _return variable yet, and I wanted to work on other issues, so I had to commit.
You can commit without marking the issue as fixed by just writing "#61" somewhere in the commit message. That way the commit will be mentioned here without the issue being closed.
The base type of the array type is not set, see note on https://github.com/team-worthwhile/worthwhile/commit/1fb1df674cb960417d2579d5a136b973826bf62c#L0R1148 line 1148
Fixed in e1f9c3ae3fc10df1ef055b0cfb24fae6bf6e132d, for some reason GitHub is not displaying this.
See
testIndexedReturnVariableReference
inInterpreterAstNodeVisitorTest
, following test program:This test fails with an unknown validity interpreter error.
Debugging in
InterpreterAstNodeVisitor::getAllSymbols()
, one can see that the variablesymbolStack
is defined as follows:This means that only the variables
a
andN
are visible in the context of the postcondition, but not the return variable reference, so the return variable reference is not passed on to the prover, which promptly fails to evaluate the quantified expression.