Report not-enough-specs and no-angelic-value cases separately#239
Merged
Conversation
Contributor
|
Thanks a lot. Started CI. Would you be able to add a test case for this? |
agodio
force-pushed
the
angelic-value-report
branch
from
2294025 to
b1ec3e2
Compare
Contributor
Author
|
I've added a small regression test for this scenario, following the existing test structure. |
Contributor
|
thanks a lot @agodio |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
collectSpecificationsreturns an empty list when synthesis is not possible (i.e., when there is no angelic value). This case is now reported accordingly."Not enough specifications" is now reported when a trivial patch would satisfy the available specifications.
The counter of statements with angelic values is updated accordingly. If there is only one spec for a statement with an angelic value, the final status will be
NO_SYNTHESISinstead ofNO_ANGELIC_VALUE.