This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/48883] ?: ternary operator fails in certain contexts - link error
- From: "redi at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 1 Jul 2011 16:51:08 +0000
- Subject: [Bug c++/48883] ?: ternary operator fails in certain contexts - link error
- Auto-submitted: auto-generated
- References: <bug-48883-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48883
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> 2011-07-01 16:50:36 UTC ---
Is this related to http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49609#c2 ?
The ternary operator is not one of the contexts listed in 13.4 [over.over] p1
either. The explicit argument list uniquely identifies the specialization, so
myMax<int> is an lvalue for the function template, but I don't see any
requirement that it gets instantiated