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

[dcl.type.simple]/2 erroneous statement about a type-specifier #2909

Closed
jabelloc opened this issue May 30, 2019 · 2 comments
Closed

[dcl.type.simple]/2 erroneous statement about a type-specifier #2909

jabelloc opened this issue May 30, 2019 · 2 comments

Comments

@jabelloc
Copy link

jabelloc commented May 30, 2019

[dcl.type.simple]/2:

A placeholder-type-specifier is a placeholder for a type to be deduced ([dcl.spec.auto]). A type-specifier of the form typenameopt nested-name-specifieropt template-name is a placeholder for a deduced class type ([dcl.type.class.deduct]). . . .

AFAICT, there is no way to obtain a type-specifier with the form specified above.

@jensmaurer
Copy link
Member

jensmaurer commented May 30, 2019

It seems the grammar for typename-specifier in [temp.res] is missing an option for
nested-name-specifier template-name to make the typename prefix possible. Changes to the grammar are unlikely to be editorial. @zygoloid?

@jensmaurer jensmaurer added decision-required A decision of the editorial group (or the Project Editor) is required. and removed decision-required A decision of the editorial group (or the Project Editor) is required. labels May 30, 2019
@jensmaurer
Copy link
Member

Editorial meeting: The grammar for typename-specifier allows a trailing identifier, which does cover template-name as well. We understand "of the form" quotes are re-matching the tokens, so there is no defect.

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