{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreidrdwfanwxwdakgmyvfgcrgrnzhz7pz3ejhwegegkd4i3snsiveqa",
    "uri": "at://did:plc:pi6woz4d47bkuws673w2il2r/app.bsky.feed.post/3mni56zoqohn2"
  },
  "path": "/t/h2jvm-a-haskell-library-for-writing-jvm-bytecode/14182#post_11",
  "publishedAt": "2026-06-04T16:23:39.000Z",
  "site": "https://discourse.haskell.org",
  "textContent": "Thanks for the info. I was mostly wondering about a case such as marking something as both public and private—ideally that wouldn’t be possible, but maybe it’s last-one-wins?\n\nAlternatively, if it were an argument to `runClassBuilder` then it would be syntactically impossible to supply multiple, but then it would also be a required parameter (no defaulting).\n\nNot necessarily a big problem, it’s just the sort of thing that catches my eye with any builder pattern—how to handle restrictions based on other things done in the same “build”.",
  "title": "H2JVM - A Haskell Library for writing JVM Bytecode"
}