public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fchelnokov at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/109159] New: explicit constructor is used in copy-initialization Date: Thu, 16 Mar 2023 19:51:48 +0000 [thread overview] Message-ID: <bug-109159-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109159 Bug ID: 109159 Summary: explicit constructor is used in copy-initialization Product: gcc Version: 12.2.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: fchelnokov at gmail dot com Target Milestone: --- The following code must be accepted (as it does in Clang and MSVC): struct A { A( float ) {} template<class U> explicit A( U ) {} }; template<class T> concept CopyFromIntList = requires( T t ) { t = { 1 }; }; static_assert( !CopyFromIntList<A> ); because 't = {1}' is invalid: chosen constructor is explicit in copy-initialization. But in GCC static_assert fails. Online demo: https://gcc.godbolt.org/z/Pf47E6dno
next reply other threads:[~2023-03-16 19:51 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-16 19:51 fchelnokov at gmail dot com [this message] 2023-03-16 21:35 ` [Bug c++/109159] " pinskia at gcc dot gnu.org 2023-03-16 21:35 ` pinskia at gcc dot gnu.org 2023-03-16 21:42 ` [Bug c++/109159] [10/11/12/13 Regression] " pinskia at gcc dot gnu.org 2023-03-16 21:46 ` mpolacek at gcc dot gnu.org 2023-03-17 21:16 ` mpolacek at gcc dot gnu.org 2023-03-20 20:54 ` cvs-commit at gcc dot gnu.org 2023-03-20 20:56 ` [Bug c++/109159] [10/11/12 " mpolacek at gcc dot gnu.org 2023-03-27 14:06 ` mpolacek 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-109159-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: 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).