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

[expr.ref] p1 should use the term "sequenced" #6573

Open
Eisenwave opened this issue Sep 20, 2023 · 2 comments
Open

[expr.ref] p1 should use the term "sequenced" #6573

Eisenwave opened this issue Sep 20, 2023 · 2 comments

Comments

@Eisenwave
Copy link
Contributor

Is it intentional that the term "sequenced" is not used in [expr.ref] p1? I suspect it's just an editorial oversight.

Rather than saying "X happens; the result of X then ...", we could use "sequenced" in some way. However, I'm not sure of the exact wording.
@xmh0511
Copy link
Contributor

xmh0511 commented Sep 25, 2023

It could be

The evaluation of the postfix expression before the dot or arrow is sequenced before the evaluation of the id-expression, and the value computation of the entire postfix expression is sequenced after the value computation of both operands.

Relevant issue is #5836

@jensmaurer
Copy link
Member

The id-expression in a class member access is a compile-time thing and "evaluating" it doesn't make much sense; it doesn't have a "value" by itself. Only in conjunction with the object expression does it have a value.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@xmh0511 @Eisenwave @jensmaurer