Dynamic: add TypeModel.isTypeUsed #14120
Draft
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.
There was a bug in the design of
TypeModel, that meant when pruning models we have no way of knowing which types might be contributed via aTypeModel.This PR adds a predicate
TypeModel.isTypeUsed(type)and then implementors must use it to expose this information.To simplify its use in simple cases, the implementor is able to use the body
any()to disable all pruning.We want to be able to prune irrelevant models, and in order to generate flow summaries from a model, the pruning information cannot depend on data-flow nodes. For that reason, each language now has a recursion guard that prevents
isTypeUsedfrom depending onDataFlow::Node.