{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiad67tmilfcq4wt2lqcuho4imangbz4a3n3t5wf22k5fvghb5so5m",
    "uri": "at://did:plc:pi6woz4d47bkuws673w2il2r/app.bsky.feed.post/3mgg5nxtc6bn2"
  },
  "path": "/t/announcing-scrod-like-haddock-but-faster/13761#post_10",
  "publishedAt": "2026-03-06T17:50:14.000Z",
  "site": "https://discourse.haskell.org",
  "tags": [
    "Support module description fields · Issue #357 · tfausak/scrod · GitHub",
    "`Control.Monad`",
    "`Control.Exception`"
  ],
  "textContent": "Sure, I’ll add that. Issue here: Support module description fields · Issue #357 · tfausak/scrod · GitHub\n\nI’ve never really understood the point of those module headers though. `Module` is redundant, it’s just the module name. `Description` is also redundant, it’s just the module documentation. `Copyright`, `License`, and `Maintainer` duplicate the same fields in the package description (Cabal file). `Stability` has been hilariously useless everywhere I’ve seen it, like `Control.Monad` saying it’s “provisional”. And same for `Portability`; somehow `Control.Exception` is “non-portable”?\n\nAlso syntactically it’s annoying. Why use a custom syntax just for these fields, when there’s a perfectly good definition list syntax: `[term]: definition`?\n\nAnyway, rant aside this should be relatively simple to implement.",
  "title": "Announcing Scrod, like Haddock but faster"
}