I should add that (compared to goto or setjmp/longjmp), by making exceptions a language
thing, the compiler can attach more context to the exception event (or condition). In the
scheme I outlined, the vendor library function must declare what exceptions it doesn’t
handle and the compiler can pass more context that may not make sense to a library user
but may help its developer pinpoint the cause.
On Mar 10, 2023, at 9:28 AM, segaloco
<segaloco(a)protonmail.com> wrote:
If nothing else, I could provide much better stack traces to vendors when I'm
particularly stuck on something and convinced it isn't my fault. Maybe such a thing
exists in C# but I've never gone looking for it, all I know is catching an exception
from some vendor library with zero useful information makes me want to take a hammer to
much more than the code...