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++/51336] [C++11] is_abstract and sfinae
Date: Mon, 28 Nov 2011 21:05:00 -0000	[thread overview]
Message-ID: <bug-51336-4-IreMImfHAj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51336-4@http.gcc.gnu.org/bugzilla/>

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

Daniel Krügler <daniel.kruegler at googlemail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |daniel.kruegler at
                   |                            |googlemail dot com

--- Comment #1 from Daniel Krügler <daniel.kruegler at googlemail dot com> 2011-11-28 20:49:52 UTC ---
(In reply to comment #0)
> #include <type_traits>
> template<class T>
> struct A {
>         template<class=typename
> std::enable_if<std::is_same<T,int>::value>::type>
>                 A(A const&){}
> };
> constexpr bool b = std::is_abstract<A<double>>::value;

I *think* the compiler is right to reject this as it currently does, we have
*no* sfinae here. When you instantiate A<double>, the declaration of the
template constructor is also instantiated, but at that point A<double> is an
incomplete type.

IMO you need one further indirection, e.g.

template<class T>
struct A {
  template<class U = T, class = typename
    std::enable_if<std::is_same<U, int>::value>::type
  >
  A(A const&){}
};

Btw.: Neither of these forms can ever prevent the "real" copy constructor to be
declared, defined, and used by the compiler.

> I am not sure what is supposed to happen (that's why I tried), but this result
> doesn't seem right. Filed under C++ because is_abstract directly forwards to
> the __is_abstract builtin, but feel free to reassign to libstdc++ if you think
> the problem is there somehow.

Lets look what the compiler-intrinsic people say, above is my first guess on
that.


  reply	other threads:[~2011-11-28 20:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-28 19:30 [Bug c++/51336] New: " marc.glisse at normalesup dot org
2011-11-28 21:05 ` daniel.kruegler at googlemail dot com [this message]
2011-11-28 21:49 ` [Bug c++/51336] " marc.glisse at normalesup dot org
2011-11-29  8:49 ` daniel.kruegler at googlemail dot com
2011-11-29 10:29 ` paolo.carlini at oracle dot com
2011-11-29 10:36 ` marc.glisse at normalesup dot org
2011-11-29 10:51 ` marc.glisse at normalesup dot org
2011-11-29 11:26 ` daniel.kruegler at googlemail dot com
2011-11-29 12:02 ` marc.glisse at normalesup dot org
2011-11-29 13:00 ` daniel.kruegler at googlemail dot com
2022-02-17 10:41 ` [Bug c++/51336] [C++11] warn on inaccessible template special member functions 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-51336-4-IreMImfHAj@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).