public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/107605] GCC rejects valid program involving requires-clause Date: Thu, 10 Nov 2022 13:49:25 +0000 [thread overview] Message-ID: <bug-107605-4-6m3IdJZUDN@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 --- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> --- (In reply to Jason Liam from comment #2) > Yes i know this has nothing to do with `std::bind`. OK, good. You reported a bug with std::bind in the title, and std::bind in the example. I'm providing the necessary analysis in the bug report and a reduced example. You don't need to get defensive about it. For example, I created > the following demo that reproduces the same error without std::bind. See > demo: https://godbolt.org/z/K6jKqsGx5 Nice. That wasn't provided in the bug report. So I added the information here. If you don't want us to analyse your bug report and add detail to it, don't bother reporting it!
next prev parent reply other threads:[~2022-11-10 13:49 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 [this message] 2022-11-10 23:15 ` [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 2022-11-10 23:20 ` 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-6m3IdJZUDN@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: linkBe 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).