BMC now splits up top-level conjunction #453
Merged
Conversation
This file contains hidden or 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
kroening
force-pushed
the
bmc-top-level-conjuction
branch
from
3b858fc to
6b599ed
Compare
kroening
force-pushed
the
bmc-top-level-conjuction
branch
2 times, most recently
from
ce429cf to
ef84299
Compare
|
Rebase required to resolve conflicts. |
BMC on a property with a top-level conjunction now splits up conjunctions, to form separate sets of obligations.
kroening
force-pushed
the
bmc-top-level-conjuction
branch
from
ef84299 to
5336754
Compare
|
Rebase done |
tautschnig
approved these changes
May 3, 2024
Romy15200
pushed a commit
to Romy15200/nws
that referenced
this pull request
Aug 19, 2025
BMC now splits up top-level conjunction
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.
BMC on a property with a top-level conjunction now splits up conjunctions, to form separate sets of obligations.