-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
remove overzealous Box<ZeroSizeType> optimization #44553
remove overzealous Box<ZeroSizeType> optimization #44553
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @eddyb (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
r? @arielb1 |
@bors r+ Let's see whether this is important in practice. |
📌 Commit 916ccc5 has been approved by |
💡 This pull request was already approved, no need to approve it again.
|
📌 Commit 916ccc5 has been approved by |
…-szero-optimization, r=arielb1 remove overzealous Box<ZeroSizeType> optimization
…-szero-optimization, r=arielb1 remove overzealous Box<ZeroSizeType> optimization
…-szero-optimization, r=arielb1 remove overzealous Box<ZeroSizeType> optimization
What bug is this fixing? "Overzealous" how? |
@bstrie This was leftover cruft from before @arielb1 moved drop glue to MIR shims. All it does is skip very little code, for a very special case. It was annoying because of two reasons:
|
No description provided.