public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/99032] GCC accepts attributes on friend declarations (not definitions) Date: Tue, 11 May 2021 20:04:32 +0000 [thread overview] Message-ID: <bug-99032-4-X1NVvwitHA@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99032-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99032 --- Comment #2 from Marek Polacek <mpolacek at gcc dot gnu.org> --- Current test: class X { }; template<typename T1, typename T2> void foo (T1, T2); struct S { [[deprecated]] friend void f(); // error [[deprecated]] friend void f2() { } friend void f3 [[deprecated]] (); // error friend void f4 [[deprecated]] () { } [[deprecated]] friend void; // error [[deprecated]] friend X; // error [[deprecated]] friend class N; // error friend class [[deprecated]] N2; // error [[deprecated]] friend void foo<>(int, int); // error // FIXME: When PR100339 is resolved. //[[deprecated]] friend void ::foo(int, int); // error }; template<typename T> class node { }; template<typename T> struct A { [[deprecated]] friend T; // error [[deprecated]] friend class node<T>; // we warn template<typename> [[deprecated]] friend class A; // we warn template<typename> [[deprecated]] friend void bar () { } // OK template<typename> [[deprecated]] friend void baz (); // error };
next prev parent reply other threads:[~2021-05-11 20:04 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-09 17:39 [Bug c++/99032] New: " dangelog at gmail dot com 2021-02-09 17:44 ` [Bug c++/99032] " mpolacek at gcc dot gnu.org 2021-05-11 20:04 ` mpolacek at gcc dot gnu.org [this message] 2021-05-14 1:13 ` cvs-commit at gcc dot gnu.org 2021-05-14 1:14 ` mpolacek 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-99032-4-X1NVvwitHA@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).