public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/105693] Requires-clause constructor that is deleted is not overriding the "= default" one
Date: Wed, 26 Oct 2022 20:42:06 +0000	[thread overview]
Message-ID: <bug-105693-4-tPECzCHgTH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105693-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105693

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Requires-clause constructor |Requires-clause constructor
                   |is not selected             |that is deleted is not
                   |                            |overriding the "= default"
                   |                            |one

--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Note the Requires-clause constructor is selected as you can see if you do:
```
template<typename T, typename T1>
constexpr bool same = true;

template<typename T>
struct A {
    A() = default;
    A() requires (same<T,int>){};
};

A<int> a;
```
And see a constructor is called. Just that the "= delete" is not being
rejected.

      parent reply	other threads:[~2022-10-26 20:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-22 18:40 [Bug c++/105693] New: Requires-clause constructor is not selected fchelnokov at gmail dot com
2022-10-26 20:37 ` [Bug c++/105693] " pinskia at gcc dot gnu.org
2022-10-26 20:42 ` pinskia at gcc dot gnu.org [this message]

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-105693-4-tPECzCHgTH@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).