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.

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

Open
StephenHodgson opened this issue Dec 27, 2023 · 1 comment
Open

Asynchonous methods to not have Async suffix #665

StephenHodgson opened this issue Dec 27, 2023 · 1 comment
Labels
bug Something isn't working

Comments

@StephenHodgson
Copy link

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.

Asynchronous methods in TAP include the Async suffix after the operation name for methods that return awaitable types, such as Task, Task, ValueTask, and ValueTask.

@StephenHodgson StephenHodgson added the bug Something isn't working label Dec 27, 2023
@StephenHodgson
Copy link
Author

Should be simple enough to add Async overload without introducing breaking changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant