On Friday, July 3rd, 2026 at 8:44 PM, Marcelo Zimbres Silva via Boost <boost@lists.boost.org> wrote:
Yes, but it is important to notice that Corosio competes with Asio and increases the ecosystem fragmentation. This is not a Capy/Corosio fault and there is precedent for competing libraries in Boost, but it really hurts the overall C++ software quality, for example, when your http client uses one net lib, the database driver another and so on. Perhaps soon there will be a senders and receiver based net lib. Libraries aren't likely to support all net variations natively and interop will be more likely.
9. Are there API, naming, usability, extensibility, or implementation concerns that should be addressed?
I vote ACCEPT.
Thanks, Marcelo
Thank you for taking the time to review Capy/Corosio and for providing some insight in to the performance against similar libraries.