{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreicgdbvxwxab3o65unsvvniaiq5ivm7nluouhzufl4pbtpdhwhtcji",
    "uri": "at://did:plc:pi6woz4d47bkuws673w2il2r/app.bsky.feed.post/3mmhpq6dmlvl2"
  },
  "path": "/t/exception-annotations-lay-of-the-land/14056#post_7",
  "publishedAt": "2026-05-22T19:31:47.000Z",
  "site": "https://discourse.haskell.org",
  "tags": [
    "Original blog post",
    "the library as it is today)",
    "annotated-exception"
  ],
  "textContent": "edsko:\n\n> Personally I think the fact that `toException` clears the exception context is Very Bad ™.\n\nI 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.\n\nannotated-exceptionworks 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.",
  "title": "Exception Annotations: Lay of the Land"
}