Filtering types at call edges to handle tuples better. #128
+39
−1
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 adds a filter check at the level of outgoing edges from a call node, where the tuple index information is present. This allows for more precise filtering. For example, if you specified that a function
source(...) (Value, error)
is a source but also specified thaterror
values are filtered out of the dataflow tracking, this will now filter out using the second part of the output tuple of the calls tosource
.