public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/94149] New: __is_constructible doesn't know about C++20 parenthesized init for arrays
Date: Wed, 11 Mar 2020 18:41:41 +0000	[thread overview]
Message-ID: <bug-94149-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 94149
           Summary: __is_constructible doesn't know about C++20
                    parenthesized init for arrays
           Product: gcc
           Version: 10.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: redi at gcc dot gnu.org
  Target Milestone: ---

In C++20 this is well-formed:

  using T = int[2];
  T t(1, 2);

which means that std::is_constructible_v<int[2], int, int> should be true.

The FE intrinsic gives the wrong answer, and the std::is_nothrow_constructible
library trait isn't going to work even if the intrinsic starts to give the
right answer.


i.e. this should compile with -std=gnu++2a

#include <type_traits>

int main()
{
  using T = int[2];
  T t(1, 2);

  static_assert(__is_constructible(T, int, int));
  static_assert(std::is_constructible_v<T, int, int>);
  static_assert(std::is_nothrow_constructible_v<T, int, int>);

  return t[0];
}


a.cc: In function 'int main()':
a.cc:8:17: error: static assertion failed
    8 |   static_assert(__is_constructible(T, int, int));
      |                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
a.cc:9:22: error: static assertion failed
    9 |   static_assert(std::is_constructible_v<T, int, int>);
      |                 ~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
a.cc:10:22: error: static assertion failed
   10 |   static_assert(std::is_nothrow_constructible_v<T, int, int>);
      |                 ~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

             reply	other threads:[~2020-03-11 18:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-11 18:41 redi at gcc dot gnu.org [this message]
2020-03-11 18:47 ` [Bug c++/94149] " redi at gcc dot gnu.org
2020-03-11 19:58 ` mpolacek at gcc dot gnu.org
2020-03-11 20:29 ` ville.voutilainen at gmail dot com
2020-04-09 21:03 ` mpolacek at gcc dot gnu.org
2020-04-10 17:55 ` cvs-commit at gcc dot gnu.org
2020-04-10 17:56 ` mpolacek at gcc dot gnu.org
2020-04-21 21:19 ` cvs-commit 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-94149-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: 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).