)]}'
{
  "commit": "3d486d2ffca88d7076ef9ed14fefbf6790601e32",
  "tree": "413066c404e10374d740e93bd1de2dc052b1067e",
  "parents": [
    "d097a0cba9a42f8e37bd28d0d219e433938981ec",
    "d87d7b94f8fb2125dbbe8359d3cb084cff17c365"
  ],
  "author": {
    "name": "Jonathan Brouwer",
    "email": "jonathantbrouwer@gmail.com",
    "time": "Thu Mar 12 15:52:10 2026 +0100"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Thu Mar 12 15:52:10 2026 +0100"
  },
  "message": "Rollup merge of #153705 - aerooneqq:delegation-impl-trait-generics, r\u003dpetrochenkov\n\nAlways generate generics in delegation that match trait in trait impl scenario\n\nAfter rust-lang/rust#151864 there is a change in delegation code generation in `trait impl` cases: after rust-lang/rust#151864 we started to look at user-specified args and generate functions, whose generics may not match the signature of the function that is defined in trait. Such handling of delegation from trait impl is not correct, as the generated function should always have the same generics as its signature function in trait.\n\nThis addresses the \"Fix generic params generation in trait impl case\" future work from rust-lang/rust#151864\n\nr? @petrochenkov\n",
  "tree_diff": []
}