Add final predicate check #517
Merged
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.
Currently, required predicates are checked, if there is a seed that ensures a predicate. However, if a rule does not ensure any predicates, the anaysis does not check the required predicates at all. Therefore, if a predicate is not ensured, the analysis will never check it, i.e. implicitly it is not ensured by design. The problem is that these predicates are not reported, too. That is, the analysis marks them as not ensured, but does not report it as an RequiredPredicateError. This PR adds a final predicate check to make sure that not ensured predicates are collected and reported correctly. The problem was raised in #318
Fix #318