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++/56506] variadic class template specialization not selected as best match Date: Tue, 05 Mar 2013 20:18:00 -0000 [thread overview] Message-ID: <bug-56506-4-YZwE3cSUzL@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-56506-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56506 --- Comment #4 from Daniel Krügler <daniel.kruegler at googlemail dot com> 2013-03-05 20:18:00 UTC --- (In reply to comment #3) Presumably my judgment was a bit premature and I think there is a logical flaw in my original argumentation: I think I misinterpreted 14.5.3 p5. I'm switching to observer-mode, but your examples are quite interesting because every compiler with variadic template support that I have access to rejects them. This seems to indicate some possible unforeseen case in existing models. I have forwarded this to the core language group.
next prev parent reply other threads:[~2013-03-05 20:18 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-03-02 3:04 [Bug c++/56506] New: " mmehlich at semanticdesigns dot com 2013-03-02 18:55 ` [Bug c++/56506] " mmehlich at semanticdesigns dot com 2013-03-03 19:47 ` daniel.kruegler at googlemail dot com 2013-03-04 17:00 ` mmehlich at semanticdesigns dot com 2013-03-05 20:18 ` daniel.kruegler at googlemail dot com [this message] 2024-04-04 6:41 ` pinskia at gcc dot gnu.org 2024-04-04 6:41 ` pinskia at gcc dot gnu.org 2024-04-04 6:44 ` pinskia at gcc dot gnu.org
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-56506-4-YZwE3cSUzL@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: linkBe 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).