-
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
Suggest #[repr(C)]
instead of #[repr(C, packed, ...)]
#66206
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @estebank (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. |
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
The code was previously suggesting `#[repr(C, packed, ...)]` for incorrect uses of `repr` (e.g. `#[repr = "C"]`). This change suggests the usage of `#[repr(C)]` instead. r? @estebank ref rust-lang#61286
Merging as is, but further work is needed to detect specific cases like writing @bors r+ |
📌 Commit 3fa8692 has been approved by |
cc @petrochenkov -- I believe the intent with these suggestions is that they should suggest hint at the formal grammar; not necessarily semantically valid combinations. |
☀️ Test successful - checks-azure |
The code was previously suggesting
#[repr(C, packed, ...)]
for incorrect uses ofrepr
(e.g.#[repr = "C"]
). This change suggests the usage of#[repr(C)]
instead.r? @estebank
Ref: #61286.