-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Remove another DefiningAnchor::Bubble usage #113294
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @lcnr (or someone else) soon. Please see the contribution instructions for more information. Namely, in order to ensure the minimum review times lag, PR authors and assigned reviewers should ensure that the review label (
|
This comment has been minimized.
This comment has been minimized.
Those failing tests were the ones I was talking about -- we could bump the logic in |
oof... yea, at least all the cases are now hard errors, instead of just some 😆 |
This comment was marked as resolved.
This comment was marked as resolved.
); | ||
} | ||
hir::OpaqueTyOrigin::TyAlias { .. } => { | ||
cx.tcx.sess.emit_err(OpaqueHiddenInferredBoundErr { |
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.
hard errors in rustc_lint
is somewhat :/
I also don't think we should error (or even lint, for that matter) here, tho
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.
opened a zulip thread about this https://rust-lang.zulipchat.com/#narrow/stream/315482-t-compiler.2Fetc.2Fopaque-types/topic/nested.20opaque.20bounds
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.
From a technical perspective, yeah, we shouldn't be doing hard errors inside of the lint infrastructure I think.
☔ The latest upstream changes (presumably #113377) made this pull request unmergeable. Please resolve the merge conflicts. |
This has become obsolete. |
This doesn't affect anything, but removes one difference between the new and the old solver.
r? @lcnr
cc #113278