Re: Capy Review

Andrzej Krzemienski via Boost <[email protected]> Thu, 25 Jun 2026 20:08:16 +0200

Newsgroups	gmane.comp.lib.boost.devel
Message-ID	<CAOenAXgN37J20RQWdmBPM75AE6q=w7J1PCFcA=10ER6TrNbskg@mail.gmail.com>

czw., 25 cze 2026 o 15:12 Vinnie Falco via Boost <[email protected]>
napisał(a):

>
> Asio got many things right. Capy takes those things and expresses them with
> a coroutine-native API. Or as I like to call it: coroutine-ONLY.
>

About this "Asio got many things right" statement. It looks like it
presupposes that the community here universally agrees that design
decisions in ASIO are right. With my limited knowledge about the problem
domain, I have no reasons to believe otherwise, but the design of ASIO is
known to have been criticised, for instance in wg21.link/p2464r0.
Coroutines in C++ bring a new perspective, new capabilities perhaps, and
new expectations. These may be an additional reason to question the design
in ASIO. Given that Capy/Corosio authors decided to inherit the design from
ASIO (this is a design decision), it is on them to also, at least to some
extent, defend ASIO's decisions.

Regards,
&rzej;
_______________________________________________
Boost mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://lists.boost.org/mailman3/lists/boost.lists.boost.org/
Archived at: https://lists.boost.org/archives/list/[email protected]/message/7TGZKZE6DDVZBRNH4YCUQMIYPPRU3SST/