-
Notifications
You must be signed in to change notification settings - Fork 12.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deduplicate ParamCandidates with the same value except for bound vars #84559
Conversation
// the same except for unused bound vars. Just pick the current one (the should | ||
// both evaluate to the same answer). This is probably best characterized as a | ||
// "hack", since we might prefer to just do our best to *not* create essentially | ||
// duplicate candidates in the first place. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe we want to pick the one with fewer bound vars? it'd be nice to be more deterministic here
This fixes a regression that slipped into beta 1.53, nominating for backport. |
Status on this: discussed with @nikomatsakis a change he'd like to see here. Just have to get some time to implement it. |
@bors r+ |
📌 Commit c1ef0f3 has been approved by |
@bors rollup=never p=1 we want this into master and backported soon, but I also want perf individually on it (no need to prerun) |
☀️ Test successful - checks-actions |
…ulacrum [beta] backports First-ish round of beta backports: * [beta] backport for rust-lang#84769 rust-lang#84969 * [beta] Bump stage0 to production 1.52.0 rust-lang#84994 * Deduplicate ParamCandidates with the same value except for bound vars rust-lang#84559
Fixes #84398
This is kind of a hack. I wonder if we can get other types of candidates that are the same except for bound vars. This won't be a problem with Chalk, since we don't really need to know that there are two different "candidates" if they both give the same final substitution.
r? @nikomatsakis