On Monday, July 6th, 2026 at 5:44 PM, Mateusz Fila via Boost <boost@lists.boost.org> wrote:
In particular, the name `IoAwaitable` suggests a close association with I/O, whereas the protocol actually describes a convention for sharing an execution context that is independent of I/O and can be applied to arbitrary asynchronous operations. A name that reflects this more general role might better communicate the abstraction that Capy provides.
Your use-case really highlights the need to give more thought to the naming of the protocol. It would seem to be far too narrow.
---
Verdict
I vote ACCEPT.
I really appreciate you taking the time to review the libraries and share your real-world implementation experience, especially because it homes in on the capability of Capy outside of I/O. I found it very valuable. Thank you, Mateusz.