Provide better type hints when a type doesn't support a binary operator #110877
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.
For example, when checking whether
vec![A] == vec![A]
holds, we first evaluate the LHS's ty, then probe for anyPartialEq
implementations for that. If none is found, we report an error by evaluatingVec<A>: PartialEq<?0>
for fulfillment errors, but the RHS is not yet evaluated and remains an inference variable?0
!To fix this, we evaluate the RHS and equate it to that RHS infer var
?0
, so that we are able to provide more detailed fulfillment errors for whyVec<A>: PartialEq<Vec<A>>
doesn't hold (namely, the nested obligationA: PartialEq<A>
doesn't hold).Fixes #95285
Fixes #110867