public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jens.maurer at gmx dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/111923] default argument is not treated as a complete-class context of a class
Date: Sat, 03 Feb 2024 20:08:28 +0000	[thread overview]
Message-ID: <bug-111923-4-KrnUqx7x89@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111923-4@http.gcc.gnu.org/bugzilla/>

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

Jens Maurer <jens.maurer at gmx dot net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jens.maurer at gmx dot net

--- Comment #12 from Jens Maurer <jens.maurer at gmx dot net> ---
In general, we want to be rather careful that the layout of the non-static data
members of a class cannot depend on properties of other non-static data members
that are visible due to some "complete class" rules.

Otherwise, it's way too easy to construct cycles.

      parent reply	other threads:[~2024-02-03 20:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-22 22:42 [Bug c++/111923] New: " stsp at users dot sourceforge.net
2023-10-22 22:51 ` [Bug c++/111923] " pinskia at gcc dot gnu.org
2023-10-22 22:56 ` pinskia at gcc dot gnu.org
2023-10-22 22:58 ` pinskia at gcc dot gnu.org
2023-10-22 23:04 ` stsp at users dot sourceforge.net
2023-10-22 23:08 ` pinskia at gcc dot gnu.org
2023-10-22 23:27 ` stsp at users dot sourceforge.net
2023-10-23  8:05 ` stsp at users dot sourceforge.net
2023-10-24 10:25 ` stsp at users dot sourceforge.net
2023-10-24 23:16 ` richard-gccbugzilla at metafoo dot co.uk
2023-10-24 23:30 ` stsp at users dot sourceforge.net
2023-10-25  1:35 ` stsp at users dot sourceforge.net
2024-02-03 20:08 ` jens.maurer at gmx dot net [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-111923-4-KrnUqx7x89@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).