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: Tue, 29 Nov 2011 11:26:00 -0000	[thread overview]
Message-ID: <bug-51336-4-CPsA9MDhrP@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

--- Comment #7 from Daniel Krügler <daniel.kruegler at googlemail dot com> 2011-11-29 10:50:37 UTC ---
(In reply to comment #5)
> All right, now the is_abstract behavior is settled, do you think the fixed code
> provided by Daniel in comment #1 should produce a warning, since the
> declaration is absolutely useless (I may be missing something)? 

IMO a warning could be very useful here (at least in circumstances where the
constructor is never reachable).

> Or maybe there are legitimate meta-programming tricks I am not thinking of that 
> would turn regular constructors into pseudo copy constructors to disable them?

While it seems that the current defect in regard to concept-constrained member
functions mentioned in c++std-core-20783 is a defect, so that

template<ObjectType T>
class A {
 requires SomeConcept<T>
 A(const A&) {}
};

is *intended* to work, I currently see no such chance for sfinae-constrained
special-member functions - unless the new temploid nomenclature shows that in

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

A<T>::A(A const&) is considered as a temploid as well. I stay tuned to see how
"temploids" will be defined...

Your suggested addition of a copy-constructor to non-const is surely useful in
some cases, but I think the emulation is imperfect. Just consider that you try
to copy from a source that is not const.


  parent reply	other threads:[~2011-11-29 10:51 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 ` [Bug c++/51336] " daniel.kruegler at googlemail dot com
2011-11-28 21:49 ` 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 [this message]
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-CPsA9MDhrP@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).