-
Notifications
You must be signed in to change notification settings - Fork 18
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
Assign value of an array using another array #464
Comments
I am not sure if Flint support this. Because it can compile when |
This is actually a known verifier issue, and is related to #436, and can be currently fixed by provided many type-level modifies identifiers. There is work being done on this right now in matteobilardi/flint which should hit later today. |
…el rather than type level properties - Two new AST passes to correct mutates type-level specification issues, fixing flintlang#434 flintlang#436 and hopefully fixing flintlang#464 1. Generates called constructor information 2. Updates the mutates statement using the properties of the states mutates variables and the constructor calling information - New semantic analysis extension to check as much as possible at that level that only the correct variables are mutated, as Boogie implementation does it this will enforce it by identifier - Corrected setter mutation variable identifier - Improved array and dictionary field access error messages - Fixed test suite to conform with improvements
Unfortunately it appears that this issue goes a little deeper, there seem to be some mutated array variables that aren't handled correctly by the verifier |
Is it possible to support such assignment:
Also, this now gives an
Illegal modification of variable not declared in 'mutates(...)'
errorThe text was updated successfully, but these errors were encountered: