❔ ✅ Rider is out of its mind about `async` code
I updated Rider and now it wants me to return tasks straight instead of awaiting them, as in
instead of
and wants me to use
The first one is a bad practice since it leads to bad stack traces, and the second one is arguable at best, bad practice at worst.
What changed?
instead of
and wants me to use
.ConfigureAwait()The first one is a bad practice since it leads to bad stack traces, and the second one is arguable at best, bad practice at worst.
What changed?
