- Title
- Acceptable decltype-specifiers used as nested-name-specifiers
- Status
- cd3
- Section
- _N4567_.5.1.1 [expr.prim.general]
- Submitter
- Mike Miller
Created on 2012-01-05.00:00:00 last changed 152 months ago
Messages
Date: 2012-10-15.00:00:00
[Moved to DR at the October, 2012 meeting.]
Date: 2012-02-15.00:00:00
Proposed resolution (February, 2012): Add the following immediately after the grammar in
_N4567_.5.1.1 [expr.prim.general] paragraph 8 and move the text following
that point into a new paragraph: The type denoted by a decltype-specifier in a
nested-name-specifier shall be a class or enumeration
type. A nested-name-specifier that denotes a class...
Date: 2017-02-06.00:00:00
The current wording of the Standard does not describe what happens
when a decltype-specifier is used as a
nested-name-specifier and the type denoted by the
decltype-specifier is neither a class type nor an
enumeration type. Such nested-name-specifiers should be
prohibited, presumably somewhere around paragraphs 8-10 of
_N4567_.5.1.1 [expr.prim.general]. (The corresponding prohibition for
named types is handled as part of lookup in 6.5.5 [basic.lookup.qual] paragraph 1.)
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2014-03-03 00:00:00 | admin | set | status: drwp -> cd3 |
| 2013-05-03 00:00:00 | admin | set | status: dr -> drwp |
| 2012-11-03 00:00:00 | admin | set | messages: + msg4127 |
| 2012-11-03 00:00:00 | admin | set | status: ready -> dr |
| 2012-02-27 00:00:00 | admin | set | messages: + msg3697 |
| 2012-02-27 00:00:00 | admin | set | status: open -> ready |
| 2012-01-05 00:00:00 | admin | create | |