News for hackers. Stuff that matters.
Re:Async2 – The .NET Runtime Async experiment concludes by louthy on Thursday August 22, 2024 @08:59AM (#41319762)
Presumably, it just means there needs to be explicit forking of the green thread for cpu bound operations, otherwise everything will run synchronously (because there’s no point where the green thread is paused to wait for an IO IRQ).

That is unless your compiler or JIT injects occasional yields into your synchronous code!

Re:Async2 – The .NET Runtime Async experiment concludes by adgjlsfhk1 on Thursday August 22, 2024 @10:58AM (#41321054)
Jits already have to do this for GC so it's actually free
Re:Async2 – The .NET Runtime Async experiment concludes by Rohansi on Thursday August 22, 2024 @09:51AM (#41320256)
And that wouldn't be great for performance.
Re:Async2 – The .NET Runtime Async experiment concludes by 01HNNWZ0MV43FF on Thursday August 22, 2024 @11:26AM (#41321350)
The overhead for epoch stopping like wasm uses can be something like 1%. I did a synthetic test with native code once because I was curious.

I think Go also injects yields into its generated code for go routine scheduling