{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihxrr5xf3ao23xotrjo2ujzrj4atua7qxnqt6k436e2n2mpoemnxi",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mgswvdnw7ri2"
  },
  "path": "/t/pre-feature-request-suppress-unused-variable-warning-for-unit-type-arguments/24065#post_13",
  "publishedAt": "2026-03-11T17:12:37.000Z",
  "site": "https://internals.rust-lang.org",
  "tags": [
    "@RalfJung",
    "@Vorpal"
  ],
  "textContent": "@RalfJung I am not entirely sure this proposal is worth it myself (which is why I didn't just file an enhancement request on the compiler) but does it make more sense to you if I say that the main thing I don't like about shutting up the warning with a leading `_`, in this case, is that I will then have to _remove_ that leading `_` when, inevitably, the subcommand grows some options?\n\n@Vorpal The `struct` itself has to exist because that's how `clap` works, and it has to be supplied as an argument to the subcommand run function in order to keep the API between `main` and the subcommand run functions uniform. Again, the goal is to keep churn to an absolute minimum when, inevitably, options are added to subcommands that didn't have them.",
  "title": "Pre-feature request: suppress unused variable warning for unit-type arguments"
}