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

CWG2964 [conv.lval] Reading "invalid pointer values" #645

Open
opensdh opened this issue Nov 22, 2024 · 1 comment
Open

CWG2964 [conv.lval] Reading "invalid pointer values" #645

opensdh opened this issue Nov 22, 2024 · 1 comment

Comments

@opensdh
Copy link

opensdh commented Nov 22, 2024

Reference (section label): [conv.lval]

Issue description:

CWG2822 disambiguated that pointer values don't get replaced with invalid pointer values, but merely become invalid in the context of evaluations not inside the duration of their referenced region of storage. However, /3.3 still uses "invalid pointer value" (with a strange cross reference).

Suggested resolution:

Use the valid-in-context wording, or else just strike the bullet assuming that any lvalue-to-rvalue transformation takes place only when the result is used in an evaluation, triggering the rule in [basic.compound].

@jensmaurer jensmaurer changed the title [conv.lval] Reading "invalid pointer values" CWG2964 [conv.lval] Reading "invalid pointer values" Dec 5, 2024
@jensmaurer
Copy link
Member

CWG2964

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