I completely agree. I remember advocating heavily for the adoption of being part of a lot of the design discussions around this feature (Original blog post, the library as it is today), and I do not at all recall this being a thing anyone needed or wanted. annotated-exception works today and on older GHCs and does not contain these warts nearly as much; but it is unfortunately limited for library development because it forces all consumers of your library to adopt annotated-exception and deal with the AnnotatedException wrapper. My next plan for the library is to figure out how to incorporate the new ExceptionContext changes without ruining the utility and UX of the library.
Home AI Coding Balances Self-Host, APIs, Subscriptions