)]}'
{
  "commit": "48fd217e51cb83f4e8b33335534029da009afa48",
  "tree": "a0baeae73eee84b5b8f0330a21823cd34478184d",
  "parents": [
    "27a11b496e3a3ac17770426e1f603638cef76b50",
    "5b3e42a5627c162b00f70a07d131242f588ef299"
  ],
  "author": {
    "name": "Jacob Pratt",
    "email": "jacob@jhpratt.dev",
    "time": "Sun Nov 01 21:24:03 2026 -0500"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Sun Nov 01 21:24:03 2026 -0500"
  },
  "message": "Rollup merge of #162819 - kpreid:must-use-advice, r\u003dfmease\n\nMake the suggestion message of `unused_must_use` scarier.\n\nThe old message, “help: use `let _ \u003d ...` to ignore the resulting value”, contains no indication that this is something that you might not want to do, and in fact can be read as saying that one *should* do this.\n\nThe new message, “help: if you wish to disregard this recommendation and immediately drop the value, use `let _ \u003d ...`”, is intended to make it clear that this is a choice, and choosing it has the particular effect of immediately dropping the value.\n\nA possible further improvement, not part of this change, might be to distinguish between types that are `must_use` and have a destructor (whose side-effects are likely relevant), and types that are `must_use` and do not have a destructor, where the timing is irrelevant and the consequence is just ignoring information that was provided. However, not every destructor is relevant to `must_use`; for example, `Result\u003c(), Box\u003cdyn Error\u003e\u003e` has a destructor and is `must_use`, but the destructor is only managing memory for the error value and it has no side effects relevant to the caller (unless the error in the box has side effects of its own).\n\nInspired by [#t-lang \u003e Lint for assigning drop guards to _](https://rust-lang.zulipchat.com/#narrow/channel/213817-t-lang/topic/Lint.20for.20assigning.20drop.20guards.20to.20_/with/624036822)\n\n@rustbot label +A-lints +L-unused_must_use\n",
  "tree_diff": []
}
