On: C++ coroutines: Understanding the compiler transfo...

[synergy20]

Good to know. std::async for simple and less intensive cases, for anything serious std::thread might be the way to go, before executors is real that is.

[candiodari → synergy20]

Except you can have thousands of std::async threads, and at best a few dozen std::threads.

[jcelerier → candiodari]

That's only if the implementation uses a thread pool, I think only MSVC does it, not libstdc++ or libc++ last time I checked

[synergy20 → candiodari]

It does not scale per the youtube talk though, the promises/futures are competing with shared resource, which is a surprise.