public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vanyacpp at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/108219] New: requirement fails on a valid expression
Date: Sat, 24 Dec 2022 22:04:29 +0000	[thread overview]
Message-ID: <bug-108219-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 108219
           Summary: requirement fails on a valid expression
           Product: gcc
           Version: 12.2.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: vanyacpp at gmail dot com
  Target Milestone: ---

This code compiles OK on clang, MSVC and GCC prior to 12:

template <typename T>
concept test = requires
{
    new T[1]{{ 42 }};
};

struct foobar
{
    foobar(int);
};

int main()
{
    static_assert(test<foobar>);
    new foobar[1]{{ 42 }};
}

But on GCC 12 it produces an error:

<source>:14:19: error: static assertion failed
   14 |     static_assert(test<foobar>);
      |                   ^~~~~~~~~~~~
<source>:14:19: note: constraints not satisfied
<source>:2:9:   required by the constraints of 'template<class T> concept test'
<source>:2:16:   in requirements  [with T = foobar]
<source>:4:5: note: the required expression 'new T(1)' is invalid, because
    4 |     new T[1]{{ 42 }};
      |     ^~~~~~~~~~~~~~~~
<source>:4:5: error: could not convert '<brace-enclosed initializer list>()'
from '<brace-enclosed initializer list>' to 'foobar'
    4 |     new T[1]{{ 42 }};
      |     ^~~~~~~~~~~~~~~~
      |     |
      |     <brace-enclosed initializer list>

I believe the error is incorrect and that this is a regression in GCC 12.

             reply	other threads:[~2022-12-24 22:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-24 22:04 vanyacpp at gmail dot com [this message]
2022-12-24 23:33 ` [Bug c++/108219] [12/13 Regression] " pinskia at gcc dot gnu.org
2022-12-27 12:35 ` [Bug c++/108219] [12/13 Regression] requirement fails on a valid expression since r12-5253-g4df7f8c79835d569 marxin at gcc dot gnu.org
2023-01-09 13:42 ` rguenth at gcc dot gnu.org
2023-02-22 17:19 ` ppalka at gcc dot gnu.org
2023-03-01 19:09 ` cvs-commit at gcc dot gnu.org
2023-03-01 19:11 ` [Bug c++/108219] [12 " ppalka at gcc dot gnu.org
2023-03-03  9:35 ` vanyacpp at gmail dot com
2023-04-28 22:13 ` cvs-commit at gcc dot gnu.org
2023-04-28 22:16 ` ppalka 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-108219-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).