public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/111113] Cannot define friend function of a local class in namespace scope
Date: Wed, 23 Aug 2023 17:59:24 +0000	[thread overview]
Message-ID: <bug-111113-4-ox2Aa4OlA2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111113-4@http.gcc.gnu.org/bugzilla/>

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2023-08-23

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Confirmed.

Another testcase which might show what is really going on:
```
auto foo() {
    struct A;
    void bar(const A&);
    struct A { 
        friend void bar(const A&);
    };
    bar(A{});
    return A{};
}

using A = decltype(foo());
void bar(const A&) {}

int main()
{
        bar(foo());
}
```
We get the following error message:
```
<source>: In function 'int main()':
<source>:16:12: error: call of overloaded 'bar(foo()::A)' is ambiguous
   16 |         bar(foo());
      |         ~~~^~~~~~~
<source>:12:6: note: candidate: 'void bar(const A&)'
   12 | void bar(const A&) {}
      |      ^~~
<source>:5:21: note: candidate: 'void bar(const foo()::A&)'
    5 |         friend void bar(const A&);
      |                     ^~~
```
Which is not correct as bar in this case is the same bar.

  reply	other threads:[~2023-08-23 17:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-23  9:16 [Bug c++/111113] New: " fchelnokov at gmail dot com
2023-08-23 17:59 ` pinskia at gcc dot gnu.org [this message]
2023-08-23 18:05 ` [Bug c++/111113] " pinskia at gcc dot gnu.org
2023-08-23 18:10 ` pinskia at gcc dot gnu.org
2023-08-23 18:16 ` pinskia at gcc dot gnu.org
2023-08-23 23:30 ` language.lawyer at gmail dot com

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-111113-4-ox2Aa4OlA2@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).