)]}'
{
  "commit": "085c58f2c0c7db692a2eaf2b8970ff474eed9183",
  "tree": "327db0a3d6a8d8d5c762c1cb4d84cf9c8b1711e9",
  "parents": [
    "ea5573a6c6e5e932f917ec4a8e6d8efdeb9f394d",
    "9012d4ecb86ff245b24cc79c6c754a501244b175"
  ],
  "author": {
    "name": "bors",
    "email": "bors@rust-lang.org",
    "time": "Sat Mar 07 13:06:24 2026 +0000"
  },
  "committer": {
    "name": "bors",
    "email": "bors@rust-lang.org",
    "time": "Sat Mar 07 13:06:24 2026 +0000"
  },
  "message": "Auto merge of #153387 - Zalathar:call-query, r\u003dnnethercote\n\nGet rid of `QueryVTable::call_query_method_fn`\n\n\n\nCalling the query method to promote a value is equivalent to doing a cache lookup and then calling `execute_query_fn`, so we can just do that manually instead.\r\n\r\nThere are two “functional” differences here: If a cache hit occurs, we don\u0027t record the hit for self-profiling, and we don\u0027t register a read of the dep node. In the context of promotion, which touches *all* eligible cache entries just before writing the memory-cached values to disk, those two steps should be unnecessary overhead anyway.\r\n\r\nr? nnethercote (or compiler)",
  "tree_diff": []
}