Proposed resolution (February, 2014) [SUPERSEDED]:

1. Change Clause 11 [class] paragraph 3 as follows:

If a class is marked with the class-virt-specifier final and it appears as a base-type-specifier class-or-decltype in a base-clause (11.7 [class.derived]), the program is ill-formed. Whenever a class-key is followed...

2. Change the grammar in 11.7 [class.derived] paragraph 1 as follows:

base-specifier:
attribute-specifier-seq_opt base-type-specifier class-or-decltype
attribute-specifier-seq_opt virtual access-specifier_opt base-type-specifier class-or-decltype
attribute-specifier-seq_opt access-specifier virtual_opt base-type-specifier class-or-decltype
class-or-decltype:
nested-name-specifier_opt class-name
nested-name-specifier template simple-template-id
decltype-specifier
base-type-specifier:
class-or-decltype
access-specifier:
...

3. Delete paragraph 4 and change paragraph 5 of 13.3 [temp.names] as follows, splitting paragraph 5 into two paragraphs and moving the example from paragraph 4 into paragraph 5:

When the name of a member template specialization appears after . or -> in a postfix-expression or after a nested-name-specifier in a qualified-id, and the object expression of the postfix-expression is type-dependent or the nested-name-specifier in the qualified-id refers to a dependent type, but the name is not a member of the current instantiation (13.8.3.2 [temp.dep.type]), the member template name must be prefixed by the keyword template. Otherwise the name is assumed to name a non-template. [Example: ... —end example]

A name prefixed by the keyword template shall be a template-id or the name shall refer to a class template or alias template. [Note: The keyword template may not be applied to non-template members of class templates. —end note] The nested-name-specifier (_N4567_.5.1.1 [expr.prim.general]) of

• a class-head-name (Clause 11 [class]) or enum-head (9.8.1 [dcl.enum]) (if any) or

• a qualified-id in a declarator-id (9.3 [dcl.decl]),

or a nested-name-specifier directly contained in such a nested-name-specifier (recursively), shall not be of the form

nested-name-specifier template simple-template-id ::

[Note: That is, a simple-template-id shall not be prefixed by the keyword template in these cases. —end note]

The keyword template is optional in a typename-specifier (13.8 [temp.res]), elaborated-type-specifier (9.2.9.5 [dcl.type.elab]), using-declaration (9.10 [namespace.udecl]), or class-or-decltype (11.7 [class.derived]), and in recursively directly-contained nested-name-specifiers thereof. In these contexts, a < token is always assumed to introduce a template-argument-list. [Note: Thus, if the preceding name is not a template-name, the program is ill-formed. —end note] In other contexts, when the name of a member template specialization appears after a nested-name-specifier that denotes a dependent type, but the name is not a member of the current instantiation, the member template name shall be prefixed by the keyword template. Similarly, when the name of a member template specialization appears after . or -> in a postfix-expression (7.6.1 [expr.post]) and the object expression of the postfix-expression is type-dependent, but the name is not a member of the current instantiation (13.8.3.2 [temp.dep.type]), the member template name shall be prefixed by the keyword template. Otherwise, the name is assumed to name a non-template. [Example:

    <From original paragraph 4>

—end example] [Note: As is the case with the typename prefix...

This resolution also resolves issues 314, 343, 1794, and 1812.