public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ppalka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/111327] New: std::bind_front doesn't perfectly forward according to value category of the call wrapper object Date: Thu, 07 Sep 2023 13:16:44 +0000 [thread overview] Message-ID: <bug-111327-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111327 Bug ID: 111327 Summary: std::bind_front doesn't perfectly forward according to value category of the call wrapper object Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: ppalka at gcc dot gnu.org Target Milestone: --- Testcase: #include <functional> struct F { void operator()() & = delete; // #1 void operator()() const &; // #2 }; int main() { auto f = F{}; auto g = std::bind_front(F{}); f(); // error: use of deleted function g(); // incorrectly calls #2 instead of being ill-formed } Since f isn't invocable as a non-const lvalue, g shouldn't be either.
next reply other threads:[~2023-09-07 13:16 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-07 13:16 ppalka at gcc dot gnu.org [this message] 2023-09-12 13:13 ` [Bug libstdc++/111327] " redi at gcc dot gnu.org 2023-09-12 15:10 ` [Bug libstdc++/111327] std::bind_front (and std::not_fn) doesn't always " ppalka at gcc dot gnu.org 2023-09-12 15:27 ` cvs-commit at gcc dot gnu.org 2023-09-12 15:28 ` cvs-commit at gcc dot gnu.org 2023-09-12 15:28 ` cvs-commit at gcc dot gnu.org 2023-09-21 12:35 ` de34 at live dot cn 2023-09-28 8:36 ` de34 at live dot cn 2023-09-28 8:50 ` redi at gcc dot gnu.org 2024-01-13 4:02 ` cvs-commit 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-111327-4@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).