)]}'
{
  "commit": "4f674e6df768b18faa27422f97d4eefed806d673",
  "tree": "a2368b5a26f287d6d18a91eeb90fef20129bfeba",
  "parents": [
    "f2840cd6c85bcf0d9290eee167841ddaf2495489",
    "9e04ab69c70419f6d4057f34a09683c4ef7198cb"
  ],
  "author": {
    "name": "bors",
    "email": "bors@rust-lang.org",
    "time": "Fri Jul 18 16:27:59 2025 +0000"
  },
  "committer": {
    "name": "bors",
    "email": "bors@rust-lang.org",
    "time": "Fri Jul 18 16:27:59 2025 +0000"
  },
  "message": "Auto merge of #143845 - cjgillot:stability-query, r\u003djieyouxu\n\nSplit-up stability_index query\n\nThis PR aims to move deprecation and stability processing away from the monolithic `stability_index` query, and directly implement `lookup_{deprecation,stability,body_stability,const_stability}` queries.\n\nThe basic idea is to:\n- move per-attribute sanity checks into `check_attr.rs`;\n- move attribute compatibility checks into the `MissingStabilityAnnotations` visitor;\n- progressively dismantle the `Annotator` visitor and the `stability_index` query.\n\nThe first commit contains functional change, and now warns when `#[automatically_derived]` is applied on a non-trait impl block. The other commits should not change visible behaviour.\n\nPerf in https://github.com/rust-lang/rust/pull/143845#issuecomment-3066308630 shows small but consistent improvement, except for unused-warnings case. That case being a stress test, I\u0027m leaning towards accepting the regression.\n\nThis PR changes `check_attr`, so has a high conflict rate on that file. This should not cause issues for review.\n",
  "tree_diff": []
}