{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreif2zoh2bhhxtbb2kxukpph5xi4ip7fuob3apa535bqmqmwjj3f27u",
    "uri": "at://did:plc:pi6woz4d47bkuws673w2il2r/app.bsky.feed.post/3mgdgfrwsyf52"
  },
  "path": "/t/announcing-scrod-like-haddock-but-faster/13761#post_3",
  "publishedAt": "2026-03-05T16:13:25.000Z",
  "site": "https://discourse.haskell.org",
  "textContent": "Yup, that’s exactly right!\n\nFor name resolution, Scrod has enough information to _guess_ , but it can’t tell for certain. So it doesn’t even try. But in theory something consuming Scrod’s output could try to do ad hoc name resolution using the list of imported modules.\n\nAnother consequence of no type checking is that the module may not even compile! This is actually really useful with the VSCode extension, because you can preview documentation while you’re editing a module (as long as there are no parse errors, of course).",
  "title": "Announcing Scrod, like Haddock but faster"
}