{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreighniqfrjokhq5xqyekzjqbx56vdrn6fvnmv6unrx2debzcjkh25y",
    "uri": "at://did:plc:pi6woz4d47bkuws673w2il2r/app.bsky.feed.post/3mnwsormqg4c2"
  },
  "path": "/t/haskells-missing-mutable-reference-type/14248?page=2#post_32",
  "publishedAt": "2026-06-10T13:05:09.000Z",
  "site": "https://discourse.haskell.org",
  "textContent": "tomjaguarpaw:\n\n> What is “this feature”? Your “contextual”?\n\nYes, worker threads carrying tables of references with table size defined at compilation time.\n\ntomjaguarpaw:\n\n> I’m pointing out it’s not the library that declares the implicit configuration, it’s the caller.\n\nWould this make for a good point of abstraction though? I’d expect a given library to need several internal values be adjustable, not some interface type like `Logger`.\n\nConsider something simpler with no extra inputs whatsoever, like adjustable numeric precision or `getArgs`.",
  "title": "Haskell's missing mutable reference type"
}