Refactor/move abstract interpreter functionality into goto analyzer 1 #7120
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.
The first part of moving functionality that is basically "run the abstract interpreter and then ..." from
goto-instrument
togoto-analyzer
. I'm doing this to remove duplication of functionality, add configurability (the options ongoto-analyzer
are not completely orthogonal but they are a lot better than at the moment), add testing and to try to slim downgoto-instrument
so that it is a bit more closer to it's original intent of performing goto-model to goto-model transformations. Please say if you disagree with this as a line of refactoring.This will also provide a more radical alternative than #7111 to resolving some of the issues with #7041.