)]}'
{
  "commit": "22b4b28a7032d6f73666e5dcae4d4528c21cc7a2",
  "tree": "d0ad018db234fdb54b7c08280fa90d385e28c1bf",
  "parents": [
    "36c0285e939349ac8980d2d3b08ac99e9830ab9b",
    "f86d694bf361ef4de076d849630177a802ea238d"
  ],
  "author": {
    "name": "Jonathan Brouwer",
    "email": "jonathantbrouwer@gmail.com",
    "time": "Mon Jun 15 13:33:24 2026 +0200"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Mon Jun 15 13:33:24 2026 +0200"
  },
  "message": "Rollup merge of #157872 - qaijuang:fix-suspicious-double-ref-op-type, r\u003dcamelid\n\n`suspicious_double_ref_op`: report unadjusted return type\n\n`suspicious_double_ref_op` uses the adjusted expression type to distinguish a no-op call from a double-reference operation. When the result is used as another method\u0027s receiver, that type can include the parent method\u0027s receiver adjustment.\n\nFor example, `file.clone().write(\u0026[])` reports that `clone` returns `\u0026mut \u0026File`, even though it returns `\u0026File`.\n\nThis PR continues to use the adjusted type for lint classification, but now uses the method call\u0027s unadjusted type in the diagnostic. The same issue affects `.deref()`, so the regression test covers both operations.\n\nFixes rust-lang/rust#146227\n",
  "tree_diff": []
}