-
Notifications
You must be signed in to change notification settings - Fork 10
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
limited quantifiers in properties #5
Comments
smt aligned "forall" and "exists" keywords for these notions seem good. |
|
commit was target bad issue number |
yanntm
added a commit
that referenced
this issue
May 11, 2022
…up-java-3 Bump actions/setup-java from 2 to 3
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
there is no real reason we could not use the parameters in the property specification, we having some kind of AndAll/OrAll (or forAll, forAny) quantifiers + bool expr over parameters would be nice
e.g. viking
typedef vik_t = 0..3;
property safe [reachable] : win==1 && forAll($vik : vik) { Soldier_state[$vik]==2 };
syntax to be discussed, but that forall is a boolean Expr.
The text was updated successfully, but these errors were encountered: