)]}'
{
  "commit": "fb6879d7d996422add38a4a7070e2e6970f1b8d6",
  "tree": "c7c0bfe8cad34548e24cf5aeb476214ee3be9ea0",
  "parents": [
    "54c75a646139d9833477301c08cdef9208174f75",
    "6741efa81442bf638b240acfcb0886d54be2ac91"
  ],
  "author": {
    "name": "Jacob Pratt",
    "email": "jacob@jhpratt.dev",
    "time": "Thu Jul 09 20:09:28 2026 -0400"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Thu Jul 09 20:09:28 2026 -0400"
  },
  "message": "Rollup merge of #158877 - Enselic:adjust-best_blame_constraint, r\u003dfee1-dead\n\nborrowck: Keep returned `path` from `best_blame_constraint()` consistent\n\nThe function `fn best_blame_constraint()` returns a `Vec\u003cOutlivesConstraint\u003e` and a `BlameConstraint`. The `BlameConstraint` is really just a slimmed down version of an `OutlivesConstraint`. So we can remove `BlameConstraint` entirely and instead return `Vec\u003cOutlivesConstraint\u003e` and an index into that `Vec`. (Encapsulated in a struct for nice ergonomics.)\n\nTo prepare for that, change the code to adjust `Vec\u003cOutlivesConstraint\u003e` in-place and return info about the adjusted element, rather than returning info for a newly created \"fake\" `OutlivesConstraint`.\n\nIt is slightly sad that we make `path` `mut`, but I think we can live with that. Diagnostics tests will surely catch if someone messes up because of that.\n\nThis takes us one step closer (this is commit 2 of 4) towards the end result illustrated in https://github.com/rust-lang/rust/pull/158623.\n",
  "tree_diff": []
}