-
Notifications
You must be signed in to change notification settings - Fork 147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle IAsyncEnumerable and ValueTask returning methods in VSTHRD103 #702
Handle IAsyncEnumerable and ValueTask returning methods in VSTHRD103 #702
Conversation
Bumps [Microsoft.Diagnostics.Runtime](https://github.com/Microsoft/clrmd) from 2.0.145301 to 2.0.151903. - [Release notes](https://github.com/Microsoft/clrmd/releases) - [Changelog](https://github.com/microsoft/clrmd/blob/master/doc/ReleaseNotes2.0.md) - [Commits](https://github.com/Microsoft/clrmd/commits) Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
This corrects a regression made earlier in this branch.
Shouldn't this call `DisposeAsync` or is there some compiler magic happening?
…iter` Reverts part of 44d9db7
Update VSTHRD112.md to call `DisposeAsync` on `System.IAsyncDisposable`
@cezarypiatek How would a change to VSTHRD103 fix a bug in VSTHRD002? |
Ah, I see. #633 incorrectly believes that VSTHRD002 would report the diagnostic, but really it is VSTHRD103's responsibility. :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The fix looks good. I've written a test to repro #633 and a ValueTask returning variant of it, as this PR suggests. The test change led to a regression in another test, so I'm working to fix that, then I will merge this PR. Thank you!
Thanks for merging |
I think this might fix #633