-
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
Erase regions before calculating layout for packed field capture #92242
Conversation
(rust-highfive has picked a reviewer for you, use r? to override) |
cc: @arora-aman who wrote #82878, and @nikomatsakis who approved it. Assume y'all know this code best. |
Should I add a test for this? Is there a test flag for the existing |
I think this change is fine. We erase regions in any information we carry forward in writeback anyway. That said Niko or Mattew probably understand the possible edge cases way better than I do. |
@bors r+ |
📌 Commit 1458687 has been approved by |
…askrgr Rollup of 8 pull requests Successful merges: - rust-lang#92242 (Erase regions before calculating layout for packed field capture) - rust-lang#93443 (Add comment on stable_hash_impl for OwnerNodes) - rust-lang#93742 (Drop rustc-docs from complete profile) - rust-lang#93852 (rustdoc: remove support for multi-query search) - rust-lang#93853 (Make all `hir::Map` methods consistently by-value) - rust-lang#93861 (Fix ICE if no trait assoc const eq) - rust-lang#93862 (Split x86_64-apple builder into two) - rust-lang#93864 (Remove ArchiveBuilder::update_symbols) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
Self-explanatory. We just erase region inferencing because we don't need that for layout computation... Q: layouts are always equal modulo regions, right?
Fixes #92240