public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "daniel.kruegler at googlemail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/56421] Non-matching overload produces template substitution error
Date: Fri, 22 Feb 2013 22:01:00 -0000	[thread overview]
Message-ID: <bug-56421-4-YRaqbHCsMu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56421-4@http.gcc.gnu.org/bugzilla/>


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56421

--- Comment #7 from Daniel Krügler <daniel.kruegler at googlemail dot com> 2013-02-22 22:01:18 UTC ---
(In reply to comment #4)
> I think 13.3 [over.match] ¶2 and 13.3.1 [over.match.funcs] ¶7  say the function
> template specialization must be generated before the number of arguments is
> checked to see if the candidate function is viable.

After a cross-check with the core language group I completely agree with
Jonathan and exactly because of the paragraphs he quoted. Further-on, the
example is ill-formed, but no diagnostics required, as of [temp.inst]p6: 

"If the overload resolution process can determine the correct function to call
without instantiating a class template definition, it is unspecified whether
that instantiation actually takes place."

This sentence explains the implementation divergence (Thanks to Richard Smith
for reminding me to this part).


  parent reply	other threads:[~2013-02-22 22:01 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-21 20:02 [Bug c++/56421] New: " kristian.spangsege at gmail dot com
2013-02-22  9:09 ` [Bug c++/56421] " mpolacek at gcc dot gnu.org
2013-02-22 10:42 ` redi at gcc dot gnu.org
2013-02-22 10:59 ` daniel.kruegler at googlemail dot com
2013-02-22 16:25 ` redi at gcc dot gnu.org
2013-02-22 18:05 ` kristian.spangsege at gmail dot com
2013-02-22 18:48 ` redi at gcc dot gnu.org
2013-02-22 22:01 ` daniel.kruegler at googlemail dot com [this message]
2013-02-22 22:17 ` redi at gcc dot gnu.org
2013-02-22 23:10 ` kristian.spangsege at gmail dot com
2013-02-22 23:11 ` kristian.spangsege at gmail dot com
2013-02-22 23:20 ` redi at gcc dot gnu.org
2013-02-22 23:39 ` kristian.spangsege at gmail dot com
2013-02-22 23:46 ` kristian.spangsege at gmail dot com
2013-02-23  0:03 ` kristian.spangsege at gmail dot com
2013-02-23  0:29 ` redi at gcc dot gnu.org
2013-02-23  0:31 ` redi at gcc dot gnu.org
2013-02-23  1:35 ` kristian.spangsege at gmail dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-56421-4-YRaqbHCsMu@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).