Handle recursive TAIT item bounds - #160711
Open
amirHdev wants to merge 1 commit into
Open
Conversation
Signed-off-by: Amirhossein Akhlaghpour <m9.akhlaghpoor@gmail.com>
rustbot
added
S-waiting-on-author
amirHdev
marked this pull request as ready for review
August 8, 2026 06:50
rustbot
added
the
S-waiting-on-review
rustbot
removed
the
S-waiting-on-author
Collaborator
|
r? @khyperia rustbot has assigned @khyperia. Use Why was this reviewer chosen?The reviewer was selected based on:
|
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
3 participants
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 rust-lang/trait-system-refactor-initiative#288
Avoiding normalizing the exact opaque instance currently being checked while continuing to normalize unrelated aliases and it also adds a small fast path in SolverRelating after resolving inference variables inside non-rigid aliases if both sides are identical we skip creating an unnecessary normalization goal
the next revision of the regression failed with item does not constrain Foo::{opaque#0} while the current solver accepts it