Re: We have a new standard!

On Sun, 29 Dec 2024 11:57:45 -0500
Sam <sam@email-scan.com> gabbled:

Muttley@dastardlyhq.com writes:

I looked at co-routines and wondered wtf the author(s) was smoking. How its
supposed to be simpler than simply using a local state machine beats the  fsckout of me.

>
Everything will make sense to you when you look at the co-routines  proposal, and note its authorship:
>
https://isocpp.org/files/papers/N4402.pdf

Don't know either of the authors but I knew it was MS.

Visual C++ does not have an impressive track record of zippy adoptions of  new C++ language feature. Most of the time it gets beaten to the punch by  gcc. Weirdly, it was the first out of the gate with co-routines.
>
As I said: std::thread blows chunks on Windows. This was Microsoft's  solution.

For solution read hack. At best its co-operative multitasking reinstated in
a hideously overcomplicated way requiring nonsense special classes for [reasons] when a simple "yield" command would have sufficed.
A proper solution would be to fix whatever fuckups they've made in their
implementation of std::thread unless the problem lies in the windows kernel
itself which frankly wouldn't surprise me.