-
Notifications
You must be signed in to change notification settings - Fork 249
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
Asynchonous methods to not have Async suffix #665
Comments
Should be simple enough to add |
I don't disagree, but such changes bring the danger of breaking the API. There's also no technical benefit, so this will be a low priority. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Asynchonous methods do not properly conform to the industry standard naming conventions for Task-based Async Pattern (TAP), which stipulate to add
Async
suffix to the name of the methods to clearly show that they are awaitable.The text was updated successfully, but these errors were encountered: