)]}'
{
  "commit": "7180fd16595bbd906dcef2f35f388fe17effc4de",
  "tree": "dc768b968165fe9a00e2b5ff3976387eef59a302",
  "parents": [
    "5fb00f2f2871d21ceaedd2e737e662b8a61be408",
    "7f6f52276159ed9d175f98c950adfa2306d46b44"
  ],
  "author": {
    "name": "Matthias Krüger",
    "email": "476013+matthiaskrgr@users.noreply.github.com",
    "time": "Wed Dec 17 18:46:17 2025 +0100"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Wed Dec 17 18:46:17 2025 +0100"
  },
  "message": "Rollup merge of #150051 - Zalathar:thir-pat, r\u003dNadrieril\n\nmir_build: Rename `TestCase` to `TestableCase`\n\nIn the spirit of rust-lang/rust#149946, this is another renaming of something I\u0027ve always found confusing.\n\nWhen lowering match conditions, there is a subtle distinction between the kind of *test* being performed (on a scrutinee place), the possible outcomes of that test, and the different “cases” (corresponding to pattern nodes) that the test is distinguishing. Cases imply a particular preferred test, but once a test is chosen it can also interact with other cases as well.\n\nI have often mixed up `TestKind` and `TestCase`, since the names are so similar, and they share several variant names. Therefore, this PR renames `TestCase` to `TestableCase`, to emphasise that these are the things selected by whatever test is being performed.\n\nThere should be no change to compiler behaviour.\n",
  "tree_diff": []
}