czw., 9 lip 2026 o 20:43 toast27--- via Boost <boost@lists.boost.org> napisał(a):
Steve Gerbino wrote:
pon., 6 lip 2026 o 16:32 Steve Gerbino via Boost < boost@lists.boost.org> napisał(a): Toast27, Steve, could you show an example of what is meant by "corosio doesn't forcibly rethrow exceptions"?
I saw this in the capy:
When no result handler is provided, the result is discarded. An exception that goes unhandled (no error handler was supplied, or a handler let one escape) calls std::terminate. To react to an error, pass an error handler; it receives the std::exception_ptr and should handle it in place rather than rethrowing. To catch an error, co_await the work inside a coroutine and use try/catch rather than launching it fire-and-forget.
Thank you. I assumed that meant std::terminate would be called closer to where the
exception was thrown, making things easier for me to debug.
That is likely the case, indeed. Regards, &rzej;
_______________________________________________ Boost mailing list -- boost@lists.boost.org To unsubscribe send an email to boost-leave@lists.boost.org https://lists.boost.org/mailman3/lists/boost.lists.boost.org/ Archived at: https://lists.boost.org/archives/list/boost@lists.boost.org/message/4M62WFDA...