Save Failing Refinements in RefinedVariable #170
Open
rcosta358 wants to merge 2 commits intocontext-history-improvementsfrom
Open
Save Failing Refinements in RefinedVariable #170rcosta358 wants to merge 2 commits intocontext-history-improvementsfrom
RefinedVariable #170rcosta358 wants to merge 2 commits intocontext-history-improvementsfrom
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR allows the context debugger in the VS Code extension to show the failing assertions of a refined variable, by adding an extra field
failingRefinementto theRefinedVariableclass, and update it when the SMT check fails.Examples
Based on
context-history-improvements. After #159 is merged, the target branch should be changed tomain.