)]}'
{
  "commit": "0ae3fd93a3a91460c1957fa38fa9514decbcdf23",
  "tree": "5714f5e822044607c8c46e836894afdabdafe7ae",
  "parents": [
    "3657478e54136745873fba5495b2f9c7e197d3b9",
    "8de399ac7b7cce3314f4f7e2cd2e1285b1608e14"
  ],
  "author": {
    "name": "Jonathan Brouwer",
    "email": "jonathantbrouwer@gmail.com",
    "time": "Wed Aug 26 08:01:00 2026 +0200"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Wed Aug 26 08:01:00 2026 +0200"
  },
  "message": "Rollup merge of #161796 - fmease:rm-dead-underscore-recovery, r\u003dmu001999\n\nRemove dead parse error recovery (underscores in expressions)\n\nBack in https://github.com/rust-lang/rust/pull/63337/changes/b7f7756566c9e10983ee51bc97afe9852838299a (2019) the parser was extended to recover from `_`s as elements of tuple expressions (this was later extended to also cover call expressions). At the time, `_` obviously wasn\u0027t an expression yet.\n\nNowadays `parse_expr_res` will *always* successfully parse `_` as an `ExprKind::Underscore` (irrespective of the passed `Restrictions`). Consequently, we will never reach the special case in `parse_expr_catch_underscore`. Drop this entire wrapper function.\n\n\u003csub\u003e(No LLM was or will be used by me during the entire creation process of this PR)\u003c/sub\u003e\n",
  "tree_diff": []
}