.NET 5.0 - Hackdot

Re:.NET 5.0 by asyncawaaait on Tuesday November 10, 2020 @02:22PM (#25050364)

Awaiting a storage operation (ie. look up user) in C# will allow other calls to proceed until the I/O is available to read.

Synchronous code locks you into the model of handling one request per thread.

Given the minor overhead (both cognitive and runtime) of a sync/await, I can’t see why you wouldn’t want to do it here.

[ Parent | on HN ]

Re:.NET 5.0 by balfirevic on Tuesday November 10, 2020 @02:31PM (#25050515)

Because async/await infects everything it touches and forces me to spread irrelevant junk words all over the code which have nothing to do with the task I'm trying to accomplish.

[ Parent | on HN ]

Re:.NET 5.0 by hackerfromthefu on Tuesday November 10, 2020 @08:17PM (#25054451)

What about the far worse stack traces and debugging?

Whats a way to get the utility of normal debugging while using async?

[ Parent | on HN ]

Re:.NET 5.0 by asyncawaaait on Tuesday November 10, 2020 @08:31PM (#25054565)

Stack traces were massively improved in 2.1.

Using a good IDE (Rider or Visual Studio), debugging async/await code works as expected.

Are you doing interop or calling unmanaged code?

[ Parent | on HN ]

Re:.NET 5.0 by hackerfromthefu on Wednesday November 11, 2020 @04:44AM (#25056981)

Thanks, I will make sure to check this out. Does anyone have any articles or documentation on this?

[ Parent | on HN ]

Re:.NET 5.0 by benaadams on Wednesday November 11, 2020 @08:17PM (#25065216)

Stacktrace improvements in .NET Core 2.1: Intelligible stack traces for async, iterators and Dictionary (key not found)

https://www.ageofascent.com/2018/01/26/stack-trace-for-excep...

[ Parent | on HN ]

Re:.NET 5.0 by hackerfromthefu on Tuesday November 17, 2020 @05:59AM (#25122282)

Awesome! Thank you. Wonderful to see these open source contributions to .NET.

[ Parent | on HN ]