You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it is better to not use the suffix at all. To my opinion, the suffix was introduced in the beginning of async, when there was a sync and an async version of the same method, so there should be a difference in naming for the compiler, otherwise, it would raise an error. But a function name should tell what it does, not how he does it.
We are now at the time that most of our code uses async methods and there are no sync versions of the same method, so why should you decorate all the methods with async? Only when you have both versions the suffix makes sense,
It would be nice if the option to not suggest the async suffix becomes global and not only for test methods.
I'd like it if the extension would tell me when I end a non-async method name with
Async
.This comes up sometimes when I convert something to async and then convert it back.
The text was updated successfully, but these errors were encountered: