| ▲ | wofo 3 hours ago |
| Awesome stuff, as usual in .NET releases! The runtime async support is surprising to me... I get that stack traces are more friendly without state machines in the code, but I didn't expect they could switch to a runtime version and have equivalent performance. Cool! |
|
| ▲ | pjmlp 2 hours ago | parent [-] |
| They did that after the learnings with experiment of having a Erlang, Go, Java like implementation for async, await. |
| |
| ▲ | jayd16 2 hours ago | parent [-] | | Is this a joke, like "hen's teeth"? Those languages don't have async/await. | | |
| ▲ | shellac an hour ago | parent | next [-] | | They don't need to mark functions as needing special compilation / rewriting to support asynchronous use since the runtime provides the necessary mechanism to pause and resume (e.g. stackful continuations). So 'async' is unnecessary and 'await' can be a library function (or remain a keyword of course). | |
| ▲ | pjmlp an hour ago | parent | prev [-] | | No joke at all, not that I said "like implementation", not that they have async/await. https://github.com/dotnet/runtimelab/issues/2398 Be sure to read all the way to the bottom, |
|
|
