3 ms·
I agree with most of the author’s reasoning and 100% of their recommendations. > As the coroutines are, I don’t quite know what they’re for. They seem like the
by gumby 5y ago
I agree with most of the author’s reasoning and 100% of their recommendations.
> As the coroutines are, I don’t quite know what they’re for. They seem like they might be useful, but nobody seems excited by them.
It’s interesting that these two sentences were written next to each other.
I get the (outsider’s) impression that they were written using something like ASIO as the standard use case, which is indeed one of long-lived coroutines. I’m not sure anyone else participated who had a different application.
The second observation “nobody seems excited by them” is generally waved away by saying “get it into the standard so library writers can add sugar” (which implies that such sugar will make it into the c++26 or 29, if at all).
I’m generally pretty happy with the direction the committee has been moving in since C++17 or even 14. But I agree coroutines don’t seem to have quite made it.
- vlovich123 5y agoA coworker added coroutines to KJ [1] so for our purposes it’s “made it”. It’ll be more broadly useful obviously with library support in the standard. I think that’s targeted for c++23 [1] https://github.com/capnproto/capnproto/blob/master/kjdoc/tour.md#coroutines https://github.com/capnproto/capnproto/blob/master/kjdoc/tou...