public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/48521] New: [4.5/4.6/4.7 Regression] [C++0x] std::result_of doesn't work with pointer to member
Date: Fri, 08 Apr 2011 21:16:00 -0000	[thread overview]
Message-ID: <bug-48521-4@http.gcc.gnu.org/bugzilla/> (raw)

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

           Summary: [4.5/4.6/4.7 Regression] [C++0x] std::result_of
                    doesn't work with pointer to member
           Product: gcc
           Version: 4.6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: redi@gcc.gnu.org


This is supposed to work, and did with 4.4:

#include <functional>
struct X
{
  int foo();
};

typedef int (X::*pm)();
std::result_of<pm()>::type i = 0;

This means we don't accept std::async(X::foo, ...) which is defined in terms of
result_of

I think I intentionally removed support for pointers to members from result_of,
because an earlier C++0x draft said it shouldn't work


             reply	other threads:[~2011-04-08 21:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-08 21:16 redi at gcc dot gnu.org [this message]
2011-04-08 21:16 ` [Bug libstdc++/48521] " redi at gcc dot gnu.org
2011-04-09 10:55 ` redi at gcc dot gnu.org
2011-04-16 19:53 ` redi at gcc dot gnu.org
2011-04-16 23:12 ` paolo.carlini at oracle dot com
2011-04-17 20:28 ` redi at gcc dot gnu.org
2011-04-18 21:44 ` redi at gcc dot gnu.org
2011-04-19 13:26 ` redi at gcc dot gnu.org
2011-04-19 13:28 ` [Bug libstdc++/48521] [4.5/4.6 " redi at gcc dot gnu.org
2011-04-23 17:51 ` redi at gcc dot gnu.org
2011-04-23 17:55 ` [Bug libstdc++/48521] [4.5 " redi 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-48521-4@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).