VSTHRD002 no longer warns on Task.Result/Wait/GetResult/etc after Task.WhenAll (in cases where proved to be safe) #878
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.
Closes #693 (I think there's a typo in which it refers to VSTHRD103 but the warning comes from VSTHRD002)
VSTHRD002 now checks if the task has completed via
Task.WhenAll
prior to the problematic member access (e.g.Result
,Wait
,GetResult
), and that the task variable has not been used in a way that would invalidate this test.No longer produces VSTHRD002 warnings
Correctly produces VSTHRD002 warnings because task variable is modified after WhenAll
Still (incorrectly) produces VSTHRD002 warnings
Cases like these are too difficult / impossible to prove with static analysis.
EDIT: On second thought, that last example might be possible.