Implementation of the Claim Deducer that tracks influence #6888
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
Introduced an AnalysisResult class to track nodes within the visitor. Passes all existing unit tests.
After thinking about it, I don't think this is necessary right now. The Claim Deducer is only used in test code, and thus will be stripped out by ProGuard. Later, when the deducer is ready to be incorporated into DFA, we can wrap the invocation of |
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.
An attempt at a clean implementation of the Paxel claim deducer. This PR takes notes from #6547 as well as internal discussions.
TODO:- [ ] Wrap with build flag