)]}'
{
  "commit": "fead508238c2a840323404332f7a63358ebccf7d",
  "tree": "aa4299974b117d7babfbc0ebeed47ee427ab2198",
  "parents": [
    "ee40e0267cc25c903769880409deeba526cd9be2",
    "696690ba21b6b4739093bddf811499b8daa845b1"
  ],
  "author": {
    "name": "Stuart Cook",
    "email": "Zalathar@users.noreply.github.com",
    "time": "Fri Nov 14 13:14:00 2025 +1100"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Fri Nov 14 13:14:00 2025 +1100"
  },
  "message": "Rollup merge of #148812 - Zalathar:expansions, r\u003dJonathanBrouwer\n\ncoverage: Associate hole spans with expansion tree nodes\n\nThis PR is another incremental step towards expansion region support in coverage instrumentation.\n\nWhen preparing coverage mappings for a function, we extract “raw” spans from MIR, and then use “hole” spans extracted from HIR to avoid overlap with nested items and closures. That hole-carving process was historically built around the assumption that there would be one set of spans and holes per function, but expansion region support will need to invalidate that assumption.\n\nTherefore, to be more friendly to future work on expansion regions, this PR associates each hole span with its corresponding node in the expansion tree, and makes the span refinement step obtain holes from the current node.\n\nThere should be no change to compiler output.\n",
  "tree_diff": []
}