public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/48113] [4.6/4.7 Regression] [C++0x] bind with tuple argument fails
Date: Mon, 14 Mar 2011 17:24:00 -0000	[thread overview]
Message-ID: <bug-48113-4-lyoEHdOIBe@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48113-4@http.gcc.gnu.org/bugzilla/>

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

Jason Merrill <jason at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
         AssignedTo|unassigned at gcc dot       |jason at gcc dot gnu.org
                   |gnu.org                     |

--- Comment #4 from Jason Merrill <jason at gcc dot gnu.org> 2011-03-14 17:24:36 UTC ---
SFINAE is not removing an overload; it doesn't work like that.  SFINAE only
applies to function templates, not non-template member functions of class
templates.  It's just that for some reason we aren't complaining about the
functor case.  Reduced further:

struct A { };
volatile A& f();

struct F1
{
  void operator()(A);
};

typedef void (*F2)(A);

typedef decltype (F1()(f())) t1;
typedef decltype (F2()(f())) t2;

The inconsistency is odd.  I would expect both lines to give an error.


  parent reply	other threads:[~2011-03-14 17:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-14 14:02 [Bug libstdc++/48113] New: " martin.kronbichler at it dot uu.se
2011-03-14 14:09 ` [Bug libstdc++/48113] " redi at gcc dot gnu.org
2011-03-14 14:19 ` [Bug libstdc++/48113] [4.6 Regression] " redi at gcc dot gnu.org
2011-03-14 14:26 ` [Bug libstdc++/48113] [4.6/4.7 " rguenth at gcc dot gnu.org
2011-03-14 16:23 ` redi at gcc dot gnu.org
2011-03-14 17:24 ` jason at gcc dot gnu.org [this message]
2011-03-14 17:34 ` jason at gcc dot gnu.org
2011-03-14 17:56 ` paolo.carlini at oracle dot com
2011-03-14 18:02 ` redi at gcc dot gnu.org
2011-03-14 18:04 ` redi at gcc dot gnu.org
2011-03-14 18:10 ` redi at gcc dot gnu.org
2011-03-14 18:48 ` [Bug c++/48113] " jason at gcc dot gnu.org
2011-03-14 18:59 ` redi at gcc dot gnu.org
2011-03-16 20:03 ` jason at gcc dot gnu.org
2011-03-16 20:04 ` jason at gcc dot gnu.org
2011-03-16 20:24 ` jason 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-48113-4-lyoEHdOIBe@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).