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++/80637] constraint on a member function does causes ambigious and not allowing forming a pointer to the function
Date: Thu, 10 Nov 2022 23:24:30 +0000 [thread overview]
Message-ID: <bug-80637-4-899S3gHxAM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-80637-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80637
--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #4)
> Reduced testcase from the dup bug:
Oh MSVC still rejects this reduced testcase for the same reason as GCC.
<source>(19): error C3535: cannot deduce type for 'auto' from
'overloaded-function'
prev parent reply other threads:[~2022-11-10 23:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-80637-4@http.gcc.gnu.org/bugzilla/>
2022-06-21 18:03 ` [Bug c++/80637] [concepts] incorrect ambiguous overload pinskia at gcc dot gnu.org
2022-06-21 18:04 ` pinskia at gcc dot gnu.org
2022-11-10 23:20 ` pinskia at gcc dot gnu.org
2022-11-10 23:21 ` [Bug c++/80637] constraint on a member function does causes ambigious and not allowing forming a pointer to the function pinskia at gcc dot gnu.org
2022-11-10 23:24 ` pinskia at gcc dot gnu.org [this message]
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-80637-4-899S3gHxAM@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).