Use correct flag when checking if captureState assumptions need to be inserted #835
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When discharging verification conditions, Boogie optionally inserts
:captureStateassumptions into the AST. This improves error reporting in case of a proof failure. Currently, these assumptions are only inserted if the user wants to print the counterexample model to a file. However, a counterexample model is sometimes used within Boogie without being printed to a file, in which case the:captureStateassumptions should still be inserted. This PR changes the condition under which Boogie adds:captureStateassumptions to account for such scenarios.