Fix projection substitution order considering GATs #790
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.
When an
AliasEq
goal contains another alias as its self type, we generate the following clause:<<X as Y>::A as Z>::B == U :- <T as Z>::B == U, <X as Y>::A == T
, withT
being a new variable. We've been building<T as Z>::B
by swapping the first argument in the original projection's substitution withT
, but it's not the self type when the associated typeB
has generic parameters, leading to wrong subgoals.The added test would yield "No possible solution" in current master.
Also removes
ignore
attribute on a doctest that was added in #778 as GATs hit stable.Spotted in rust-lang/rust-analyzer#14164.