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++/107022] error: use of deleted function 'std::unordered_map
Date: Fri, 21 Oct 2022 15:08:07 +0000	[thread overview]
Message-ID: <bug-107022-4-QbyqcxIKJ0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107022-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 from Jonathan Wakely <redi at gcc dot gnu.org> ---
For the example in comment 0 the default-initializer for things_{} is the
problem, removing the {} allows it to compile.

For the example in Bug 107340 the problem is the default-initializer x = 0 in
the nested class, removing that allows it to compile.

The nested class is complete at the closing } but its complete class contexts
are not complete until the enclosing class is complete. default-initializers
and nested classes do not work well.

      parent reply	other threads:[~2022-10-21 15:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-23 21:58 [Bug c++/107022] New: " piersh at hotmail dot com
2022-09-23 22:00 ` [Bug c++/107022] " pinskia at gcc dot gnu.org
2022-09-23 22:05 ` pinskia at gcc dot gnu.org
2022-09-23 22:14 ` redi at gcc dot gnu.org
2022-09-23 22:16 ` piersh at hotmail dot com
2022-09-23 22:21 ` piersh at hotmail dot com
2022-09-23 22:22 ` pinskia at gcc dot gnu.org
2022-10-21  7:24 ` pinskia at gcc dot gnu.org
2022-10-21 14:03 ` jens.maurer at gmx dot net
2022-10-21 15:08 ` redi at gcc dot gnu.org [this message]

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-107022-4-QbyqcxIKJ0@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).