)]}'
{
  "commit": "772a5dd4e89edc96af5578ffebbfde7229b61234",
  "tree": "902e96454d85060f8cfee2bd531c48409c146afc",
  "parents": [
    "db3f6be4a674ee7140da859530ea42ff20fc0c77",
    "368791e6d4e3ad9e7b0981bd870700fac8978205"
  ],
  "author": {
    "name": "Jonathan Brouwer",
    "email": "jonathantbrouwer@gmail.com",
    "time": "Fri Sep 04 22:29:00 2026 +0200"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Fri Sep 04 22:29:00 2026 +0200"
  },
  "message": "Rollup merge of #162262 - sjwang05:forall-binder-ice, r\u003dBoxyUwU\n\nAvoid manually instantiating some binders in error reporting with `-Znext-solver`\n\nIf we call `enter_forall` on a binder before passing it to the new solver, the placeholders that come from instantiation get canonicalized before solving happens. This can be a problem if we end up equating one variable whose universe can\u0027t name another variable\u0027s, since the equate will succeed in the solver since canonicalization sets all universe indices to the root universe but fail when we actually construct the response with fresh vars at the correct universes, which causes an ICE. We now just hand the unopened binder to the trait solver directly, since (I believe) both solvers are able to handle that just fine.\n\nThis came up while I was looking at https://rust-lang.zulipchat.com/#narrow/channel/618216-t-types.2Fcall-for-participation/topic/next-solver.20UI.20test.20triage/with/612965995, and the `universe-error-host-effect.rs`/`poly_select` change was basically the same type of ICE that I found while investigating the first one.\n",
  "tree_diff": []
}