{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreidj5pujpcb572ta6safphwsyoyo6sxgdgpltwivumffi6j3itvrn4",
    "uri": "at://did:plc:pi6woz4d47bkuws673w2il2r/app.bsky.feed.post/3mhfnnuudkqo2"
  },
  "path": "/t/type-level-programming-dealing-with-ambiguous-type-error/13828#post_2",
  "publishedAt": "2026-03-19T08:46:38.000Z",
  "site": "https://discourse.haskell.org",
  "textContent": "The simple solution is to make x a required type argument. You can also try your luck at enabling AllowAmbiguousTypes, but maybe you’ll get an ambiguity error when you try to use eval anyway.\n\nI do think `Plus n` (given one argument) should be injective. Perhaps you can find some other way to define it which the compiler can understand. For example a typeclass with functional dependencies.",
  "title": "Type level programming: Dealing with ambiguous type error"
}