Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Suggest using ConfigureAwait(false) #26

Closed
sharwell opened this issue Nov 17, 2014 · 2 comments
Closed

Suggest using ConfigureAwait(false) #26

sharwell opened this issue Nov 17, 2014 · 2 comments
Labels
code fix diagnostic refactoring

Comments

@sharwell
Copy link
Member

This isn't fully fleshed out yet, but it would be nice to be able to identify cases where ConfigureAwait(false) definitely applies, and add it.

A refactoring could be provided for manual addition of the call in cases where code analysis was inconclusive.
@tugberkugurlu
Copy link

At first glance, diagnostic could be very tricky to suggest at the correct places as you need to be knowing the context of the code which is being executed.

I'm more for refactoring for this one.

@tugberkugurlu tugberkugurlu mentioned this issue Nov 18, 2014
Open
@BillWagner BillWagner mentioned this issue Nov 19, 2014
Open
@sharwell
Copy link
Member Author

Moved to DotNetAnalyzers/AsyncUsageAnalyzers#4.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
code fix diagnostic refactoring
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tugberkugurlu @sharwell