-
Notifications
You must be signed in to change notification settings - Fork 13k
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
Check that we don't use Rvalue::Aggregate
after the deaggregator
#75562
Conversation
79f8c97
to
9f50e14
Compare
744e74d
to
de7c836
Compare
(The force-push + squashing in one go makes it impossible to only review the delta since the last time I checked...) |
I had to rebase, but yea, I should have made separate commits for the changes since then. |
d2494de
to
03d38d4
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.
Validator and MIR pass management LGTM now.
I can't check the changes in ConstProp and generator lowering, and I don't know if the mir-opt changes make sense.
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.
I left a few minor comments but this looks great to me overall!
Since this impacts mir-optimizations: @bors rollup=never |
Co-authored-by: Wesley Wiser <[email protected]>
@bors r+ |
📌 Commit dcc2027 has been approved by |
☀️ Test successful - checks-actions, checks-azure |
fixes #75481
r? @wesleywiser
cc @RalfJung (modified the validator)