public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/105452] static_assert inside nameless nested union: invalid "inaccessible within this context" error Date: Tue, 03 May 2022 08:39:03 +0000 [thread overview] Message-ID: <bug-105452-4-S5GwRkiI4C@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105452-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105452 Martin Liška <marxin at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2022-05-03 CC| |marxin at gcc dot gnu.org, | |redi at gcc dot gnu.org Ever confirmed|0 |1 --- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> --- Confirmed.
next prev parent reply other threads:[~2022-05-03 8:39 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-02 11:27 [Bug c++/105452] New: " foobarandfoo at gmail dot com 2022-05-03 8:39 ` marxin at gcc dot gnu.org [this message] 2022-05-03 8:47 ` [Bug c++/105452] [9/10/11/12/13 Regression] static_assert inside anonymous union inside a templated struct causes " pinskia at gcc dot gnu.org 2022-05-03 13:17 ` ppalka at gcc dot gnu.org 2022-05-27 9:48 ` [Bug c++/105452] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-28 10:49 ` jakub at gcc dot gnu.org 2022-07-26 11:37 ` rguenth at gcc dot gnu.org 2023-03-30 3:14 ` jason at gcc dot gnu.org 2023-03-30 22:26 ` cvs-commit at gcc dot gnu.org 2023-07-07 10:43 ` [Bug c++/105452] [11/12/13/14 " rguenth 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-105452-4-S5GwRkiI4C@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: linkBe 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).