2 ms·
Coroutines would still run on top of std::future, it would be Just syntactic sugar to avoid callback hell via then chaining. In same case this might save some a
by gpderetta 10y ago
Coroutines would still run on top of std::future, it would be Just syntactic sugar to avoid callback hell via then chaining. In same case this might save some allocation as the callback would be a plain pointer to the control block, but that's about it.
I'm not part of the committee nor I attend meetings, but I follow the papers and the public online discussions.
- soulbadguy 10y agoFrom the last Gor paper, coroutine don't need to run on top of the std::future class. The type traits required allows for more computational patters (like generators, agent/actor, full coroutines) etc...
- gpderetta 10y agoNo, but they are still designed to work well with std::futures and that's going to be the standard blessed way to do async IO.