Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Update union/enum chapter to take RFC 2645 into account #96

Closed
nikomatsakis opened this issue Mar 7, 2019 · 0 comments · Fixed by #432
Closed

Update union/enum chapter to take RFC 2645 into account #96

nikomatsakis opened this issue Mar 7, 2019 · 0 comments · Fixed by #432
Labels
A-layout Topic: Related to data structure layout (`#[repr]`) C-editorial Category: Tracking editorial improvements to the document S-not-opsem Despite being in this repo, this is not primarily a T-opsem question

Comments

@nikomatsakis
Copy link
Contributor

RFC 2645 extends #[repr(transparent)] to unions and single variant enums. It looks likely to be accepted. We will probably need to update our layout and ABI chapter(s).
@nikomatsakis nikomatsakis added the A-layout Topic: Related to data structure layout (`#[repr]`) label Mar 7, 2019
@RalfJung RalfJung added the C-editorial Category: Tracking editorial improvements to the document label Aug 14, 2019
@RalfJung RalfJung mentioned this issue Aug 14, 2019
Closed
@JakobDegen JakobDegen added the S-not-opsem Despite being in this repo, this is not primarily a T-opsem question label Jul 25, 2023
@RalfJung RalfJung mentioned this issue Jul 25, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-layout Topic: Related to data structure layout (`#[repr]`) C-editorial Category: Tracking editorial improvements to the document S-not-opsem Despite being in this repo, this is not primarily a T-opsem question
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

add incompleteness notes RalfJung/unsafe-code-guidelines
3 participants
@nikomatsakis @RalfJung @JakobDegen