)]}'
{
  "commit": "ebdddb50133ea43ea27f41868ace2a8da43f500e",
  "tree": "c5d328741d212995e82ab82fee6f090ef8125d00",
  "parents": [
    "795a915b15ab1f7723039c40579ff8e6ae320c53",
    "1e185bdebcd14907a6d868bcb99715b581117d04"
  ],
  "author": {
    "name": "Jonathan Brouwer",
    "email": "jonathantbrouwer@gmail.com",
    "time": "Thu Sep 24 09:38:14 2026 +0200"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Thu Sep 24 09:38:14 2026 +0200"
  },
  "message": "Rollup merge of #162942 - nnethercote:rm-StashKey-AssociatedTypeSuggestion, r\u003ddavidtwco\n\nRemove `StashKey::AssociatedTypeSuggestion`\n\nCurrently it\u0027s used in a really hacky way: a diagnostic with an empty message and some suggestions is stashed. Later on it might be retrieved and its suggestions extracted. It uses `Level::Allow` so that it isn\u0027t printed by `emit_stashed_diagnostics` at shutdown if it hasn\u0027t been retrieved.\n\nThis isn\u0027t a normal stashed diagnostic, more just a case of \"save some information that might be useful for diagnostics later\". We can record the information more simply and directly.\n\nThis commit adds `paths_matching_assoc_types` fields to `Resolver` and `ResolverGlobalCtxt`. These store the spans of the paths of interest. The new subdiagnostic `AssocTypeWithSameName` is used to construct the relevant suggestions when they are needed. Much nicer. The old approach removed the stashed diagnostic and the new approach doesn\u0027t remove the set entry, so a single span could conceivably match more than once, presumably a good thing, though this doesn\u0027t show up in the test suite.\n\nr? @davidtwco\n",
  "tree_diff": []
}