-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Move polarity into PolyTraitRef
rather than storing it on the side
#131652
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
r? @Nadrieril rustbot has assigned @Nadrieril. Use |
Some changes occurred in src/tools/clippy cc @rust-lang/clippy Some changes occurred in src/tools/rustfmt cc @rust-lang/rustfmt HIR ty lowering was modified cc @fmease |
61b9dca
to
ad43c2e
Compare
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.
Looks reasonable and like a nice improvement! I lack all context particularly for the first commit though so I'll let someone more knowledgeable call this.
r? compiler
r? compiler |
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.
Looks reasonable to me as well. As to removing the hack, if no tests fail then I think we're good 🤷 You can r=Nadrieril and me after a rebase.
@rustbot author |
☔ The latest upstream changes (presumably #131662) made this pull request unmergeable. Please resolve the merge conflicts. |
ad43c2e
to
95dba28
Compare
@bors r=Nadrieril,jieyouxu |
Arguably we could move these modifiers into
TraitRef
instead ofPolyTraitRef
, but I seeTraitRef
as simply the path part of the trait ref. It doesn't really matter -- refactoring this further is much easier now.