public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "oleksandr.koval.dev at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/109623] New: constexpr restrictions are not relaxed enough
Date: Tue, 25 Apr 2023 16:36:36 +0000	[thread overview]
Message-ID: <bug-109623-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 109623
           Summary: constexpr restrictions are not relaxed enough
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: oleksandr.koval.dev at gmail dot com
  Target Milestone: ---

https://godbolt.org/z/eo8K3Ehqq

```cpp
#include <unordered_map>

struct S{
    constexpr S() = default;       // error, not implicitly constexpr
    constexpr S(){}                // this works
    std::unordered_map<int, int> m;
};

```

My understanding is that in C++23 this should be allowed because the only
restriction for constexpr constructors and destructors is the absence of
virtual base classes.

             reply	other threads:[~2023-04-25 16:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-25 16:36 oleksandr.koval.dev at gmail dot com [this message]
2023-04-25 17:14 ` [Bug c++/109623] " redi at gcc dot gnu.org
2023-04-27 16:11 ` mpolacek at gcc dot gnu.org
2023-05-16 18:26 ` 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-109623-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).