{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreigadxiybiiad5lzk45jz3sul4cm5kdb45saff62ne7kgyfbxkqf5q",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mgswv2d47sb2"
  },
  "path": "/t/pre-feature-request-suppress-unused-variable-warning-for-unit-type-arguments/24065#post_15",
  "publishedAt": "2026-03-11T18:22:05.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "zackw:\n\n> 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\nIt makes sense, but I feel like that's why, unique among many other lints, we make it possible to suppress this as simply as adding `_` rather than having to write out something like `expect(...)`. It's one character. And almost definitionally, you'll only need to change that `_` in _one_ place, because you won't have any other references to it.",
  "title": "Pre-feature request: suppress unused variable warning for unit-type arguments"
}