public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jlame646 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/21498] [c++0x] friend declaration can name non-class with class-key
Date: Wed, 07 Feb 2024 09:27:11 +0000	[thread overview]
Message-ID: <bug-21498-4-ENCDiluphd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-21498-4@http.gcc.gnu.org/bugzilla/>

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

Jason Liam <jlame646 at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jlame646 at gmail dot com

--- Comment #16 from Jason Liam <jlame646 at gmail dot com> ---
GCC still accepts the code when it is ill-formed as explained
here:https://stackoverflow.com/questions/77932976/why-is-a-type-alias-not-allowed-to-be-a-friend-class-name-in-c/77932987#77932987

Here is a demo that shows that gcc accepts the invalid code:
https://godbolt.org/z/sK8Trh5PG

  parent reply	other threads:[~2024-02-07  9:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-21498-4@http.gcc.gnu.org/bugzilla/>
2011-09-10  3:30 ` redi at gcc dot gnu.org
2024-02-07  9:27 ` jlame646 at gmail dot com [this message]
     [not found] <bug-21498-8718@http.gcc.gnu.org/bugzilla/>
2009-11-03 18:40 ` jason at gcc dot gnu dot 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-21498-4-ENCDiluphd@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).