<HTML>
<HEAD>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<TITLE>
    CWG Issue 283</TITLE>
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<STYLE TYPE="text/css">
  INS { text-decoration:none; font-weight:bold; background-color:#A0FFA0 }
  .INS { text-decoration:none; background-color:#D0FFD0 }
  DEL { text-decoration:line-through; background-color:#FFA0A0 }
  .DEL { text-decoration:line-through; background-color: #FFD0D0 }
  @media (prefers-color-scheme: dark) {
    HTML { background-color:#202020; color:#f0f0f0; }
    A { color:#5bc0ff; }
    A:visited { color:#c6a8ff; }
    A:hover, a:focus { color:#afd7ff; }
    INS { background-color:#033a16; color:#aff5b4; }
    .INS { background-color: #033a16; }
    DEL { background-color:#67060c; color:#ffdcd7; }
    .DEL { background-color:#67060c; }
  }
  SPAN.cmnt { font-family:Times; font-style:italic }
</STYLE>
</HEAD>
<BODY>
<P><EM>This is an unofficial snapshot of the ISO/IEC JTC1 SC22 WG21
  Core Issues List revision 118b.
  See http://www.open-std.org/jtc1/sc22/wg21/ for the official
  list.</EM></P>
<P>2025-09-28</P>
<HR>
<A NAME="283"></A><H4>283.
  
Template <I>type-parameter</I>s are not syntactically <I>type-name</I>s
</H4>
<B>Section: </B>9.2.9.3&#160; [<A href="https://wg21.link/dcl.type.simple">dcl.type.simple</A>]
 &#160;&#160;&#160;

 <B>Status: </B>CD1
 &#160;&#160;&#160;

 <B>Submitter: </B>Clark Nelson
 &#160;&#160;&#160;

 <B>Date: </B>01 May 2001<BR>


<P>[Voted into WP at April 2003 meeting.]</P>

<P>Although 13.2 [<A href="https://wg21.link/temp.param#3">temp.param</A>] paragraph 3 contains an
assertion that</P>

<BLOCKQUOTE>

A <I>type-parameter</I> defines its identifier to be a
<I>type-name</I> (if declared with <TT>class</TT> or
<TT>typename</TT>)

</BLOCKQUOTE>

<P>the grammar in 9.2.9.3 [<A href="https://wg21.link/dcl.type.simple#1">dcl.type.simple</A>] paragraph 1
says that a <I>type-name</I> is either a <I>class-name</I>, an
<I>enum-name</I>, or a <I>typedef-name</I>.  The <I>identifier</I>
in a template <I>type-parameter</I> is none of those.  One
possibility might be to equate the <I>identifier</I> with a
<I>typedef-name</I> instead of directly with a <I>type-name</I>,
which would have the advantage of not requiring parallel treatment
of the two in situations where they are treated the same (e.g.,
in <I>elaborated-type-specifier</I>s, see
<A HREF="245.html">issue 245</A>).  See also
<A HREF="215.html">issue 215</A>.</P>

<P><B>Proposed resolution (Clark Nelson, March 2002):</B></P>

<P>In 13.2 [<A href="https://wg21.link/temp.param#3">temp.param</A>] paragraph 3,
change "A <I>type-parameter</I> defines its identifier to be a
<I>type-name</I>"
to "A <I>type-parameter</I> defines its identifier
to be a <I>typedef-name</I>"</P>

<P>In 9.2.9.5 [<A href="https://wg21.link/dcl.type.elab#2">dcl.type.elab</A>] paragraph 2,
change "If the identifier resolves to a <I>typedef-name</I> or a template
<I>type-parameter</I>"
to "If the identifier resolves to a <I>typedef-name</I>".</P>

<P>This has been consolidated with the edits for some other
issues.  See N1376=02-0034.</P>

<BR><BR>
</BODY>
</HTML>
