Skip to content

Conversation

@AlisdairM
Copy link
Contributor

@AlisdairM AlisdairM commented Nov 6, 2025

Review [lex] for odd whitespace issues

@AlisdairM AlisdairM marked this pull request as draft November 6, 2025 13:50
@jensmaurer jensmaurer added this to the post-2025-11 milestone Nov 6, 2025
@jensmaurer jensmaurer added ballot-comment Response to an NB or ISO comment on a ballot not-editorial Issue is not deemed editorial; the editorial issue is kept open for tracking. labels Nov 6, 2025
\begin{bnf}
\nontermdef{class-head}\br
class-key \opt{attribute-specifier-seq} class-head-name \opt{class-property-specifier-seq} \opt{base-clause}\br
class-key \opt{attribute-specifier-seq} class-head-name \opt{class-virt-specifier} \opt{base-clause}\br
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should retain the rename to "class-property-specifier".
To be discussed in core.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

FWIW, if it's not too late, I would go further: my experimentation indicates that vendors generally do treat this thing as a -seq in order to diagnose mistakes like struct A final final {} as "repeated final" instead of "expected {". So I think it would actually be useful to keep P2786's whole grammar change here, not just the change of virt to property but also the addition of -seq and the sentence forbidding repetitions, as (I think) it better reflects existing practice.
Yes, even though it'd be a -seq of only a single possible specifier and repeating that specifier would be ill-formed — it's still existing practice. Or so I think.

@tkoeppe
Copy link
Contributor

tkoeppe commented Nov 6, 2025

(This seems somewhat premature; we haven't even got a motion yet.)

@AlisdairM AlisdairM closed this Nov 7, 2025
@AlisdairM AlisdairM force-pushed the revert_trivial_relocation branch from 723c495 to bb1af1a Compare November 7, 2025 07:16
@AlisdairM AlisdairM changed the title Revert "P2786R13 Trivial Relocatability for C++26" Review [lex] Nov 7, 2025
@AlisdairM AlisdairM deleted the revert_trivial_relocation branch November 14, 2025 14:18
@eisenwave eisenwave removed this from the post-2025-11 milestone Nov 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ballot-comment Response to an NB or ISO comment on a ballot not-editorial Issue is not deemed editorial; the editorial issue is kept open for tracking.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants