[Voted into WP at April 2003 meeting.]

Notes from the 4/02 meeting:

This is resolved by the proposed changes for issue 323.

Notes from 04/00 meeting:

John Spicer opined that even though Clause 13 [temp] paragraph 7 speaks of "declaring a class template exported," that does not mean that the class template is "an exported template" in the sense of paragraph 8. He suggested clarifying paragraph 7 to that effect instead of the change to paragraph 8 suggested above, and questioned the need for a change to 13.9.2 [temp.inst].

Suggested resolution:

• Change Clause 13 [temp] paragraph 8 to say that "An exported non-class template need only be declared..."
• Change 13.9.2 [temp.inst] paragraph 6 to use wording similar to that of 13.9.3 [temp.explicit] paragraph 3 regarding the requirement for a definition of the class template to be in scope.

(See also issue 212.)

Clause 13 [temp] paragraph 7 allows class templates to be declared exported, including member classes and member class templates (implicitly by virtue of exporting the containing template class). However, paragraph 8 does not exclude exported class templates from the statement that

An exported template need only be declared (and not necessarily defined) in a translation unit in which it is instantiated.

If an implicit instantiation of a class template specialization is required and the template is declared but not defined, the program is ill-formed.

A definition of a class template or a class member template shall be in scope at the point of the explicit instantiation of the class template or class member template.