-
Notifications
You must be signed in to change notification settings - Fork 13.3k
rustc_transmute: Directly use types from rustc_abi #132248
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
rustc_transmute: Directly use types from rustc_abi #132248
Conversation
Failed to set assignee to
|
These commits modify the If this was unintentional then you should revert the changes before this PR is merged. |
well! r? compiler |
r=me when green |
@bors rollup |
@bors r=compiler-errors |
Should we get rid of these reexports? RA isn't great at dealing with them so it often ends up adding the |
…iaskrgr Rollup of 4 pull requests Successful merges: - rust-lang#131391 (Stabilize `isqrt` feature) - rust-lang#132248 (rustc_transmute: Directly use types from rustc_abi) - rust-lang#132252 (compiler: rename LayoutS to LayoutData) - rust-lang#132253 (Known-bug test for `keyword_idents` lint not propagating to other files) r? `@ghost` `@rustbot` modify labels: rollup
Rollup merge of rust-lang#132248 - workingjubilee:add-rustc-abi-to-transmute, r=compiler-errors rustc_transmute: Directly use types from rustc_abi Using the reexport from rustc_target is not necessary here, so use rustc_abi directly.
...well, we want the |
But yes incrementing towards the final state where rustc_target reexports nothing, at least publicly, from rustc_abi, is the primary aim of most of my recent flurry of PRs. |
Sounds good, thanks!
|
Using the reexport from rustc_target is not necessary here, so use rustc_abi directly.