3 ms·
Two people already downvoted without replying. Tell me you have never developed complex software without actually telling me!
by pif 2y ago
Two people already downvoted without replying. Tell me you have never developed complex software without actually telling me!
- mrkeen 2y agoI didn't down-vote. > There are very few ways to use Task.Result and Task.Wait correctly I don't even speak C# and I can read between the lines enough to see that they're saying 'waiting for a non-blocking method turns it into a blocking method, undoing the work of the library implementers who worked hard to provide you with non-blocking code'. Looking at the article, I think the solution was covered in the first sentence of the first list item: > Asynchrony is viral > Once you go async, all of your callers SHOULD be async,
- deleted 2y ago[deleted]
- pif 2y ago> Once you go async, all of your callers SHOULD be async, If you can't fathom that calling code could be written before, or independently from, or in a different domain than. called code, than you've never developed complex code.