-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Normalize when collecting TAITs in signature #116819
Normalize when collecting TAITs in signature #116819
Conversation
This comment has been minimized.
This comment has been minimized.
Ah, there's that stack overflow 🤣 |
//! Test that we don't follow through projections to find | ||
//! opaque types. |
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.
Change the comments to explain what the test is testing now (same for all the other tests)
I've reworked this a bit, but as a consequence, I think we need to consider all usages of a TAIT in a signature to be defining. I'll write a bit more about why later. @rustbot author |
☔ The latest upstream changes (presumably #117076) made this pull request unmergeable. Please resolve the merge conflicts. |
I'm gonna put this on pause until we decide whether we even want to have the signature rule for TAITs @rustbot blocked |
Don't think we're gonna go with this |
Normalize before visiting when collecting opaques allowed to be defined by body.
r? oli-obk
Just putting this up for initial review, not super cleaned up yet.