Avoid presence of our internal types in generated code #1244
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.
Description
This request remove soot types and our internal types from soot classes at all, and our classes used for mocks, overrides, etc., from the construction of type storages. At the same time, it changes API for
TypeStorageclass to avoid misunderstanding of what types will it contains after its creation via different constructors.Fixes #295
Type of Change
How Has This Been Tested?
Automated Testing
There was no specific tests added. This request should not break already existed as a proof that we didn't remove anything that was required by our overridden classes.
Manual Scenario
There was no manual testing.
Checklist: