Boost.Capy and Boost.Corosio Review ResultRecommendation
I recommend that *Boost.Capy and Boost.Corosio be conditionally accepted into Boost.*
Thank you for your in-depth review of the code and for serving as review manager. I appreciate all the suggested improvements. Some of them have already been made during the review, for example delay/timeout were moved to Corosio. Capy documentation has been rewritten, although some of your suggestions still need to be addressed. I will compile a list of the conditions with a plan to address them moving forward.
*1c* Adding to Capy - io_context and signal handling?
From my professional experience writing servers purely with coroutines the io_context is the key to making signals, networking, file-io all go together smoothly. As such it seems like that fundamental construct should be in Capy.
As it exists today, Capy does not contain any OS-facing code. Capy does define execution_context which all executors derive from. All platform dependent code lives in Corosio -- which is why signals and the io_context live there.