public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "potswa at mac dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/56283] New: std::result_of does not gracefully SFINAE (not define ::type)
Date: Mon, 11 Feb 2013 04:10:00 -0000	[thread overview]
Message-ID: <bug-56283-4@http.gcc.gnu.org/bugzilla/> (raw)


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

             Bug #: 56283
           Summary: std::result_of does not gracefully SFINAE (not define
                    ::type)
    Classification: Unclassified
           Product: gcc
           Version: 4.7.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: potswa@mac.com


>From the spec of std::result_of,

If the expression INVOKE(declval<Fn>(), declval<ArgTypes>()...) is well formed
when treated as an unevaluated operand (Clause 5), the member typedef type
shall name the type decltype(INVOKE(declval<Fn>(), declval<ArgTypes>()...));
otherwise, there shall be no member type.

If the given INVOKE expression is invalid, ::type should not exist. But an
attempt to use it this way to detect a valid call fails.

Below is a short demo program. A non-overloaded function name and a functor
type with an overloaded call operator are passed to result_of through a type
traits style SFINAE wrapper. None of the cases work. In 2 of the 3 cases the
failure fires the static assertion, but not for the multiple overload issue.


#include <type_traits>

template< typename fn, typename = void >
struct is_invokable : std::false_type {};

template< typename fn >
struct is_invokable< fn, typename std::conditional< true, void, typename
std::result_of< fn >::type >::type >
        : std::true_type {};

void f( int );
static_assert( ! is_invokable< decltype( f ) &( char const * ) >(), "can
convert c-string to int" );

struct s {
    void operator() ( int ) {}
    void operator() ( float ) {}
};
static_assert( ! is_invokable< s( double ) >(), "resolved ambiguous conversion"
);
static_assert( ! is_invokable< s( char * ) >(), "converted pointer to number"
);


             reply	other threads:[~2013-02-11  4:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-11  4:10 potswa at mac dot com [this message]
2013-02-11  4:58 ` [Bug libstdc++/56283] " potswa at mac dot com
2013-02-11 10:06 ` redi at gcc dot gnu.org
2013-02-11 10:07 ` 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-56283-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).