<HTML>
<HEAD>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<TITLE>
    CWG Issue 1220</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="1220"></A><H4>1220.
  
Looking up <I>conversion-type-id</I>s
</H4>
<B>Section: </B>_N4868_.6.5.6&#160; [<A href="https://wg21.link/basic.lookup.classref">basic.lookup.classref</A>]
 &#160;&#160;&#160;

 <B>Status: </B>C++11
 &#160;&#160;&#160;

 <B>Submitter: </B>Mike Miller
 &#160;&#160;&#160;

 <B>Date: </B>2010-11-13<BR>


<P>[Voted into the WP at the March, 2011 meeting as part of paper N3262.]</P>

<P>The resolution of <A HREF="1111.html">issue 1111</A> changes
_N4868_.6.5.6 [<A href="https://wg21.link/basic.lookup.classref#7">basic.lookup.classref</A>] paragraph 7 to read,</P>

<BLOCKQUOTE>

[A] <I>conversion-type-id</I> is first looked up in the class of
the object expression and the name, if found and denotes a type,
is used.  Otherwise it is looked up in the context of the entire
<I>postfix-expression</I> and the name shall denote a type.

</BLOCKQUOTE>

<P>The result of this specification is that a non-type member
declaration in the class scope of the object expression will not
be found (although it will hide a base class type member of the
same name), but a non-type declaration in the context of the
expression will be found (and make the program ill-formed).</P>

<P>This is inconsistent with the way other lookups are handled
when they occur in a context that requires a type.  For example,
the lookup for a <I>nested-name-specifier</I> &#8220;considers
only namespaces, types, and templates whose specializations are
types&#8221; (6.5.5 [<A href="https://wg21.link/basic.lookup.qual#1">basic.lookup.qual</A>] paragraph 1); the lookup
for a name appearing in an <I>elaborated-type-specifier</I> is
done &#8220;ignoring any non-type names that have been declared&#8221;
(6.5.6 [<A href="https://wg21.link/basic.lookup.elab#2">basic.lookup.elab</A>] paragraph 2); and in the lookup for a name
in a <I>base-type-specifier</I>, &#8220;non-type names are
ignored&#8221; (11.7 [<A href="https://wg21.link/class.derived#2">class.derived</A>] paragraph 2). The lookup
for a <I>conversion-type-id</I> should be similar, and the wording
in _N4868_.6.5.6 [<A href="https://wg21.link/basic.lookup.classref#7">basic.lookup.classref</A>] paragraph 7 adjusted accordingly.</P>

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