public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "luigighiron at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/112839] New: Unable to default initialize member variable in specific circumstances
Date: Sun, 03 Dec 2023 20:54:45 +0000	[thread overview]
Message-ID: <bug-112839-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 112839
           Summary: Unable to default initialize member variable in
                    specific circumstances
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: luigighiron at gmail dot com
  Target Milestone: ---

The following code is not accepted by GCC:

struct A {
    struct B {
        int C = 0;
    };
    A() = default;
    A(int) {}
    std::pair<B, B> p;
};

The error message generated indicates that it was unable to find a constructor
to call in the constructor A(int).

Doing any of the following seems to remove the error:
1. Removing the constructor A()
2. Explicitly define the constructor A()
3. Defining a default constructor for B (that isn't defaulted)
4. Removing the default value from C
5. Initializing p when it is being declared, i.e. std::pair<B, B> p{};
6. Defining B outside of the class
7. Using a non-default constructor in the member initializer list

Clang, MSVC, and old versions of GCC (version 8, version 5, and version 4)
accept this code.

             reply	other threads:[~2023-12-03 20:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-03 20:54 luigighiron at gmail dot com [this message]
2023-12-03 21:04 ` [Bug c++/112839] " pinskia 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-112839-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).