public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rs2740 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/101113] g++ thinks constructor suppressed by a requires clause is actually a bad copy constructor Date: Tue, 22 Jun 2021 20:40:32 +0000 [thread overview] Message-ID: <bug-101113-4-QNS1CxCbiv@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101113-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101113 TC <rs2740 at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rs2740 at gmail dot com --- Comment #2 from TC <rs2740 at gmail dot com> --- https://eel.is/c++draft/class.copy.ctor#5 I don't think this code is valid. The constraint (which isn't checked until overload resolution time anyway) can't suppress the outright ill-formedness of the declaration.
next prev parent reply other threads:[~2021-06-22 20:40 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-17 19:34 [Bug c++/101113] New: " gcc at nospam dot scs.stanford.edu 2021-06-17 21:49 ` [Bug c++/101113] " redi at gcc dot gnu.org 2021-06-22 20:40 ` rs2740 at gmail dot com [this message] 2021-06-23 3:46 ` gcc at nospam dot scs.stanford.edu 2023-11-29 4:53 ` gcc at nospam dot scs.stanford.edu
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-101113-4-QNS1CxCbiv@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: linkBe 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).