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++/107605] constraint on a member function does causes ambigious and not allowing forming a pointer to the function
Date: Thu, 10 Nov 2022 23:15:30 +0000	[thread overview]
Message-ID: <bug-107605-4-vPnAXP5PYK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107605-4@http.gcc.gnu.org/bugzilla/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Blocks|101603                      |
            Summary|GCC rejects valid program   |constraint on a member
                   |involving requires-clause   |function does causes
                   |                            |ambigious and not allowing
                   |                            |forming a pointer to the
                   |                            |function

--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
At first I thought it was a pointer to member function issue but nope it is not
as the following happens too but we need to have have the class as a template
rather than the function:
extern "C" int puts(const char*);

template <typename T>
class myclass {
public:

  static void func(const T&) requires true
  {
     puts("true");
  }

  static void func(const T&) requires false
  {
     puts("false");
  }
};                                                                              

auto mylambda = &myclass<int>::func;


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101603
[Bug 101603] [meta-bug] pointer to member functions issues

  parent reply	other threads:[~2022-11-10 23:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-10  8:06 [Bug c++/107605] New: GCC rejects valid program involving std::bind and requires jlame646 at gmail dot com
2022-11-10 12:05 ` [Bug c++/107605] " redi at gcc dot gnu.org
2022-11-10 12:50 ` [Bug c++/107605] GCC rejects valid program involving requires-clause jlame646 at gmail dot com
2022-11-10 13:49 ` redi at gcc dot gnu.org
2022-11-10 23:15 ` pinskia at gcc dot gnu.org [this message]
2022-11-10 23:20 ` [Bug c++/107605] constraint on a member function does causes ambigious and not allowing forming a pointer to the function 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-107605-4-vPnAXP5PYK@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).