)]}'
{
  "commit": "abbab2d67c8738602b57aa511cf596d056d13964",
  "tree": "f3acd5ef6780ec2e914b4ec145d4628c6e4cd7f1",
  "parents": [
    "a42e95df4fe878a0995b9f6f1f3a9c5a9b47475e",
    "0ab14caeaf5f7ef987e047ccbbbdda59876f86de"
  ],
  "author": {
    "name": "Jonathan Brouwer",
    "email": "jonathantbrouwer@gmail.com",
    "time": "Wed Jun 17 22:36:25 2026 +0200"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Wed Jun 17 22:36:25 2026 +0200"
  },
  "message": "Rollup merge of #157917 - onehr:fix-for-loop-missing-in-suggestion-103561, r\u003dfolkertdev\n\nDon\u0027t suggest adding `in` to a `for` loop that already has one\n\nCloses rust-lang/rust#103561.\n\nWhen a `for` loop is missing its `in`, the parser suggested inserting one based only on the token following the pattern. For a malformed binding such as `for i i in 0..10` it therefore suggested `for i in i in 0..10`, which is itself invalid.\n\nThe suggestion is now only emitted when the loop header does not already contain an `in` before the body. The `for x EXPR` / `for x of EXPR` / `for x \u003d EXPR` suggestions are unchanged.\n",
  "tree_diff": []
}