>num += Calculate(20).Result; You're sure you should use .Result here instead of... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		tester756 on May 21, 2023 \| parent \| context \| favorite \| on: How much memory do you need to run 1M concurrent t... >num += Calculate(20).Result; You're sure you should use .Result here instead of awaiting it?

uncheckederror on May 21, 2023 [–]

To expand upon this thought, here is the AsyncGuidance doc[1] on why not to use .Result to get the return value of a completed Task in C#.

To make this simple they introduced async Main[2] a few years ago.

[1]: https://github.com/davidfowl/AspNetCoreDiagnosticScenarios/b...

[2]: https://github.com/dotnet/csharplang/blob/main/proposals/csh...

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact