public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gcc at nospam dot scs.stanford.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/107889] New: Incorrect parsing of qualified friend function returning decltype(auto)
Date: Sun, 27 Nov 2022 19:47:46 +0000	[thread overview]
Message-ID: <bug-107889-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 107889
           Summary: Incorrect parsing of qualified friend function
                    returning decltype(auto)
           Product: gcc
           Version: 12.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: gcc at nospam dot scs.stanford.edu
  Target Milestone: ---

G++ 12.2.0 rejects a valid friend declaration for a fully-qualified function
returning `decltype(auto)`.  To reproduce the problem, you can try to compile
the following code with `g++ -std=c++20 -c bug.cc`:

decltype(auto)
f()
{
}

struct S {
  friend decltype(auto) ::f();
};


This results in the following error:

$ c++ -std=c++20 -c bug.cc
bug.cc:7:27: error: 'decltype(auto)' is not a class type
    7 |   friend decltype(auto) ::f();
      |                           ^
bug.cc:7:27: error: 'decltype(auto)' is not a class type
bug.cc:7:27: error: 'decltype(auto)' is not a class type
bug.cc:7:29: error: 'decltype(auto)' is not a class type
    7 |   friend decltype(auto) ::f();
      |                             ^
bug.cc:7:10: error: ISO C++ forbids declaration of 'f' with no type
[-fpermissive]
    7 |   friend decltype(auto) ::f();
      |          ^~~~~~~~~~~~~~
bug.cc:7:29: error: invalid use of 'decltype(auto)'
    7 |   friend decltype(auto) ::f();


A similar problem was reported in bug #59766 for friend functions returning
auto.  It seems to have been mostly fixed, but the combination of
decltype(auto) and the function name being qualified (::f) is still a problem.

             reply	other threads:[~2022-11-27 19:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-27 19:47 gcc at nospam dot scs.stanford.edu [this message]
2022-11-28  6:52 ` [Bug c++/107889] " marxin at gcc dot gnu.org
2022-11-28  9:24 ` redi at gcc dot gnu.org
2022-11-28  9:28 ` redi 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-107889-4@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).