Skip to content
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

Enable checking a set of invariants and see which ones broke #1573

Open
bugarela opened this issue Dec 23, 2024 · 0 comments
Open

Enable checking a set of invariants and see which ones broke #1573

bugarela opened this issue Dec 23, 2024 · 0 comments
Labels
good first issue A simple issue to start with simulator Quint simulator UX impacts or improves user experience

Comments

@bugarela
Copy link
Collaborator

Recently, I came up with this workaround for this problem:

https://github.com/left-curve/left-curve/blob/e0609fbadc7040effd44095926899a2a52a014da/grug/jellyfish-merkle/spec/quint/apply_state_machine.qnt#L370-L391

We should make this built-in into Quint. Users should be able to provide a set (yargs array) of invariants to --invariants and we Quint should print which ones were violated.

Not sure how to do that for Apalache (verify/compile), but even if that's not possible, we should still do it for the simulator (and combine all of them into a conjunction for Apalache).

@bugarela bugarela added simulator Quint simulator UX impacts or improves user experience good first issue A simple issue to start with labels Dec 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue A simple issue to start with simulator Quint simulator UX impacts or improves user experience
Projects
None yet
Development

No branches or pull requests

1 participant