)]}'
{
  "commit": "56572203199216a87f69fa954bb1864a0ee8aade",
  "tree": "b3764b5bc124e4dfd4bb455ce7fbf26e3d5d4c71",
  "parents": [
    "333cd70b886efc0e3b67cda360341a4af39a54d1"
  ],
  "author": {
    "name": "Chayim Refael Friedman",
    "email": "chayimfr@gmail.com",
    "time": "Mon Apr 20 05:30:14 2026 +0300"
  },
  "committer": {
    "name": "Chayim Refael Friedman",
    "email": "chayimfr@gmail.com",
    "time": "Mon Apr 20 05:36:49 2026 +0300"
  },
  "message": "Do not check solver\u0027s cache validity on every access\n\nThis should help speed.\n\nInstead, we do it only when an `Interner` is constructed, since an interner cannot be held across revisions.\n\nThere is a problem, though: an interner *can* be held across different databases. To solve that, we also reinit the cache when attaching databases, and take the assumption that everything significant (i.e. that can access the cache) will need to attach the db. This is somewhat risky, but we\u0027ll take it for the speed.\n\nTheoretically we could *only* reinit on db attach, but it\u0027s less risky this way, and with-crate interner construction is rare.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "a6957c66ff0c6e6f0fec62661c9db0ce8d90074d",
      "old_mode": 33188,
      "old_path": "src/tools/rust-analyzer/crates/hir-ty/src/next_solver/infer/mod.rs",
      "new_id": "fa7aa518764bb2d60f0bb350e71e455250637dcc",
      "new_mode": 33188,
      "new_path": "src/tools/rust-analyzer/crates/hir-ty/src/next_solver/infer/mod.rs"
    },
    {
      "type": "modify",
      "old_id": "1078a6af420e9f09a372b5c2999595caf9ce4f64",
      "old_mode": 33188,
      "old_path": "src/tools/rust-analyzer/crates/hir-ty/src/next_solver/interner.rs",
      "new_id": "9ad1b3b71227c7a7d41abf7f71fbc1ed060e1485",
      "new_mode": 33188,
      "new_path": "src/tools/rust-analyzer/crates/hir-ty/src/next_solver/interner.rs"
    }
  ]
}