C#: Additional tracking of lambdas through fields and properties #15489
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 PR adds support for tracking lambdas through fields and (field-like) properties, but (currently) limited to assignments in constructors and uses in instance methods:
That is, we will track lambdas from
(1)
to(2)
, but not from(2)
to(3)
. This restriction is because the data flow algorithm for tracking lambdas is not field-sensitive, hence we need to model field stores/reads as jump steps, and therefor apply the conservative restriction above.I spot checked a few of the new results, and they are indeed the result of more lambda calls being resolvable.