On Mon, Jun 29, 2026 at 4:50 AM Udo Steinbach via Boost < boost@lists.boost.org> wrote:
I do not think a single library or a single "mechanism" for reporting errors
All conceivable error-handling mechanisms have two things in common. They all have to convert infos to text. And they need safe collect and transport. Since the collected information is of unknown—and in any case, varying—types, the transport mechanism must be a heterogeneous container.
It is implied in what you're saying, but let's be explicit -- the transport mechanism needs to be: - Type-safe (because the conversion to text needs to be postponed until an error handling scope is reached). - Dynamic (because intermediate error-neutral functions may not know at compile time all possible failures that needs to be communicated to the error handling scope).