)]}'
{
  "commit": "91a2ec32e315f81d33da4a4dc9c4b79c30eeca5e",
  "tree": "2b9ae735c8fa1ba21b3b358c7da9f23592a34305",
  "parents": [
    "c908ea27fdebc0fd0116ef37112af317e07ca8b9",
    "b4bf57b7aa46ae7dfd31c9a7468102342f91c713"
  ],
  "author": {
    "name": "Jacob Pratt",
    "email": "jacob@jhpratt.dev",
    "time": "Mon Feb 02 23:12:04 2026 -0500"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Mon Feb 02 23:12:04 2026 -0500"
  },
  "message": "Rollup merge of #151936 - Zalathar:fingerprint-style, r\u003dpetrochenkov\n\nMove the `fingerprint_style` special case into `DepKindVTable` creation\n\nI\u0027m a little bit fuzzy on *precisely* why anonymous queries are treated as having `FingerprintStyle::Opaque`, but I\u0027m pretty confident that baking this special case into the query vtable is equivalent to the current behaviour, while being marginally more efficient.\n\n(I believe this special case comes from anonymous queries not having a fingerprint in the first place, so “opaque” is just there to signal that reconstructing a key is impossible.)\n",
  "tree_diff": []
}