On Thursday, July 9th, 2026 at 7:51 AM, Andrzej Krzemienski via Boost <boost@lists.boost.org> wrote:
pon., 6 lip 2026 o 16:32 Steve Gerbino via Boost <boost@lists.boost.org> napisał(a):
On Friday, July 3rd, 2026 at 7:22 AM, toast27--- via Boost < boost@lists.boost.org> wrote:
3. I haven't read through much of the code but the corosio code looks approachable altho inline documentation is always a nice to have so that I don't have read source code or open my browser.
One painpoint for me me with beast has been that it forcibly rethrows exceptions making fatal exceptions hard to trace in gdb. I have to do `catch throw` and hope none of my dependencies are abusing exceptions. It looks like with capy, corosio doesn't forcibly rethrow exceptions, this is great!
Agreed, I'm glad you are pleased with the results so far.
Toast27, Steve, could you show an example of what is meant by "corosio doesn't forcibly rethrow exceptions"? I am confused by this statement and one way I could interpret it is "corosio conceals information about failure from its users".
I think that exercise is better left with Toast27 as I can only infer what he means. I can only assume that he means we don't catch and translate exceptions or simply avoid exceptions altogether on the hot path.