public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fchelnokov at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/104204] Ambiguity error for out of class definition of member function template in the presence of a member function of the same name
Date: Mon, 24 Jan 2022 18:54:02 +0000	[thread overview]
Message-ID: <bug-104204-4-2cWiqo6djj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104204-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Fedor Chelnokov <fchelnokov at gmail dot com> ---
Are you sure that this is a duplicate? Bug 39270 is about explicit
instantiation that is erroneously reported by GCC as specialization. And this
bug is about rejection of real explicit specialization in special
circumstances.

  parent reply	other threads:[~2022-01-24 18:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-24 14:42 [Bug c++/104204] New: " fchelnokov at gmail dot com
2022-01-24 18:19 ` [Bug c++/104204] " pinskia at gcc dot gnu.org
2022-01-24 18:54 ` fchelnokov at gmail dot com [this message]
2022-01-24 19:14 ` pinskia 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-104204-4-2cWiqo6djj@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).