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.

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

[basic.types] p4: definition of "value representation" unnecessarily vague #2105

Closed
zygoloid opened this issue Jun 7, 2018 · 0 comments
Closed
Assignees

Comments

@zygoloid
Copy link
Member

zygoloid commented Jun 7, 2018

[As discussed in CWG on 2018-06-07] Consider:

union U { int n; char c; };
U u = {.c = 123};

It is unclear in the current wording that the value representation of u includes all the bits that are part of the n member, not just the bits that are part of the c member, however that is the intent (and the upcoming compare_exchange_* wording depends on that). We should clarify that the set of bits in the value representation depends only on the type, and not on which value of that type we are considering.

@jensmaurer jensmaurer changed the title definition of "value representation" unnecessarily vague [basic.types] p4: definition of "value representation" unnecessarily vague Jun 8, 2018
@jensmaurer jensmaurer self-assigned this Jul 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants