public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/97198] __is_constructible(int[], int) should return true Date: Fri, 25 Sep 2020 19:06:51 +0000 [thread overview] Message-ID: <bug-97198-4-H8lPCZO6WP@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97198-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97198 --- Comment #3 from Marek Polacek <mpolacek at gcc dot gnu.org> --- (In reply to Jonathan Wakely from comment #2) > Hmm. It should be false for construction from no arguments i.e. > __is_constructible(int[]). > > But thanks to parenthesized aggregate init, you can actually do: > > using T = int[]; > T t(1); > > It's still true that int[] is incomplete, but in the example above you > actually construct is a int[1] not int[]. Agreed. > I think this should be an LWG issue. Yes, I'd prefer LWG guidance before making any changes here.
next prev parent reply other threads:[~2020-09-25 19:06 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-25 5:29 [Bug c++/97198] New: " kariya_mitsuru at hotmail dot com 2020-09-25 8:48 ` [Bug c++/97198] " redi at gcc dot gnu.org 2020-09-25 12:53 ` mpolacek at gcc dot gnu.org 2020-09-25 17:26 ` mpolacek at gcc dot gnu.org 2020-09-25 18:49 ` redi at gcc dot gnu.org 2020-09-25 19:06 ` mpolacek at gcc dot gnu.org [this message] 2020-10-05 11:02 ` redi at gcc dot gnu.org 2022-03-12 7:48 ` lichray at gmail dot com 2022-03-12 10:10 ` redi at gcc dot gnu.org 2022-03-14 11:51 ` redi at gcc dot gnu.org 2022-03-14 17:02 ` lichray at gmail dot com
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-97198-4-H8lPCZO6WP@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).