How to stop forgetting to await an awaitable call
Now that all those .NET code bases start to get littered with
await statements, I’m observing another phenomenon: forgetting to
await an awaitable member. Not just in the code I deal with in my day job, but a lot of users of Fluent Assertions have been running into this, especially since we introduced “async” versions such as
NotThrowAsync. You would expect that modern IDEs have become smart enough to help us with that. And indeed, both Visual Studio and Rider do, but only to an extend.