Repository navigation
Conversation
Collaborator
|
🤖 A dedicated |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
lcnr
force-pushed
the
next-solver-soundness-bug
branch
from
October 12, 2026 12:04
14f0018 to
3eee062
Compare
Collaborator
|
This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed. Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers. |
Collaborator
|
The job Click to see the possible cause of the failure (guessed by this bot) |
Contributor
|
☔ The latest upstream changes (presumably #164284) made this pull request unmergeable. Please resolve the merge conflicts by rebasing. |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
fixes #164054
this was previously fixed in #116530 and later reverted in #118736.
It impacts the new solver more than the old one as the new solver depends significantly more on region identity, see the relevant stabilization report section.
The old solver has significantly less region identity dependence. It does rely on region identity when merging candidates during normalization:
rust/compiler/rustc_trait_selection/src/traits/project.rs
Lines 103 to 107 in 69bccf0
This check results in additional ICE with the old solver while instead triggering the potentially region dependent goals check with the new one
rust/compiler/rustc_trait_selection/src/traits/query/type_op/custom.rs
Lines 94 to 95 in 14f0018
r? types