-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Add some comments, add can_define_opaque_ty
check to try_normalize_ty_recur
#118915
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Conversation
r? @jackh726 (rustbot has picked a reviewer for you, use r? to override) |
Some changes occurred to the core trait solver cc @rust-lang/initiative-trait-system-refactor |
woops r? lcnr |
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.
realized:
we really should mention how AliasRelate(<_ as Ambig>::Assoc, whatever)
ends up normalizing the alias to ?unconstrained
and it doesn't really matter that we equate it with whatever
, as these constraints do not flow out to the caller in any way.
r=me after nits |
Is the point you're trying to make that as long as we have an ambiguous alias in an alias-relate, we don't ever have inference side-effects and it'll always be ambiguous? In that case, sure, I agree, but I also don't know where we could best document this... |
e66720b
to
abdaa9f
Compare
☔ The latest upstream changes (presumably #118996) made this pull request unmergeable. Please resolve the merge conflicts. |
TODO: I'll move all this to a module-level doc. I'll also add a comment to compute_projection_goal explaining why alias-relate is being emitted directly. |
abdaa9f
to
a86f417
Compare
Type relation code was changed |
a86f417
to
427c55c
Compare
Ok, requesting a review on this PR then lol |
i still considered the r=me to apply here and thought you weren't done @bors r+ rollup |
For the record, I did rewrite the comment at the top of the alias-relate file, so I thought you wanted to read that. But thx for the r+ anyways. |
…iaskrgr Rollup of 11 pull requests Successful merges: - rust-lang#115046 (Use version-sorting for all sorting) - rust-lang#118915 (Add some comments, add `can_define_opaque_ty` check to `try_normalize_ty_recur`) - rust-lang#119006 (Fix is_global special address handling) - rust-lang#119637 (Pass LLVM error message back to pass wrapper.) - rust-lang#119715 (Exhaustiveness: abort on type error) - rust-lang#119763 (Cleanup things in and around `Diagnostic`) - rust-lang#119788 (change function name in comments) - rust-lang#119790 (Fix all_trait* methods to return all traits available in StableMIR) - rust-lang#119803 (Silence some follow-up errors [1/x]) - rust-lang#119804 (Stabilize mutex_unpoison feature) - rust-lang#119832 (Meta: Add project const traits to triagebot config) r? `@ghost` `@rustbot` modify labels: rollup
Rollup merge of rust-lang#118915 - compiler-errors:alias-nits, r=lcnr Add some comments, add `can_define_opaque_ty` check to `try_normalize_ty_recur` Follow-up from rust-lang#117278, since I was recently re-reviewing this code.
Follow-up from #117278, since I was recently re-reviewing this code.