Closed conradz closed 2 years ago
Fix should be possible in the verifier backend by resolving the branch condition to an AST node at the point of branching, which then does not require x
to be resolved after it is re-assigned.
This is actually caused by reassignment to parameters, which is not supported by Viper. This is fixed by 547baf08c21a54c739ab7fd1a7f20375f4038408.
The following example crashes because a conditional check, depending on a previous value of
x
, is required:with the following error: