CWG Issue 1413 (original) (raw)
This is an unofficial snapshot of the ISO/IEC JTC1 SC22 WG21 Core Issues List revision 118e. See http://www.open-std.org/jtc1/sc22/wg21/ for the official list.
2025-11-05
1413. Missing cases of value-dependency
Section: 13.8.3.4 [temp.dep.constexpr]Status: CD3Submitter: Richard SmithDate: 2011-11-09
[Moved to DR at the April, 2013 meeting.]
The list of cases in 13.8.3.4 [temp.dep.constexpr] paragraph 2 in which an identifier is value-dependent should also include:
- an entity with reference type and is initialized with an expression that is value-dependent
- a member function or a static data member of the current instantiation
Proposed resolution (October, 2012):
- Change 13.8.3.4 [temp.dep.constexpr] paragraph 2 as follows and move the text following the bulleted list into a new paragraph:
An
identifierid-expression is value-dependent ifit is:
- it is a name declared with a dependent type,
- it is the name of a non-type template parameter,
- it names a member of an unknown specialization,
- it names a static data member of the current instantiation that is not initialized in a member-declarator,
- it names a static member function that is a member of the current instantiation, or
- it is a constant with literal type and is initialized with an expression that is value-dependent.
Expressions of the following form...
- Change 13.8.3.4 [temp.dep.constexpr] paragraph 5 as follows:
An id-expression is value-dependent if it names a member of an unknown specialization.An expression of the form&qualified-id where the qualified-id's_nested-name-specifier_ names the current instantiation is value-dependent.