public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hewillk at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/100187] New: ranges::search_n helper lambda misses forwarding return type Date: Wed, 21 Apr 2021 16:09:44 +0000 [thread overview] Message-ID: <bug-100187-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100187 Bug ID: 100187 Summary: ranges::search_n helper lambda misses forwarding return type Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: hewillk at gmail dot com Target Milestone: --- ranges_algo.h#L565: auto __value_comp = [&] <typename _Rp> (_Rp&& __arg) { return std::__invoke(__pred, std::forward<_Rp>(__arg), __value); }; __value_comp misses forwarding the return type (-> decltype(auto)) which made the following unnecessary failed: #include <algorithm> struct Bool { operator bool() { return true; }; Bool() = default; Bool(const Bool&) = delete; }; int main() { Bool b; std::vector v{1, 0}; std::ranges::search_n(v, 1, 1, [&](auto, auto) -> Bool& { return b; }); } https://godbolt.org/z/zjn8Gz3c5
next reply other threads:[~2021-04-21 16:09 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-21 16:09 hewillk at gmail dot com [this message] 2021-04-21 16:19 ` [Bug libstdc++/100187] " hewillk at gmail dot com 2021-04-21 16:44 ` hewillk at gmail dot com 2021-04-22 6:06 ` hewillk at gmail dot com 2021-04-22 19:12 ` [Bug libstdc++/100187] Helper lambda in ranges_algo.h " ppalka at gcc dot gnu.org 2021-04-28 3:23 ` cvs-commit at gcc dot gnu.org 2021-10-13 13:51 ` cvs-commit at gcc dot gnu.org 2021-10-13 13:56 ` cvs-commit at gcc dot gnu.org 2021-10-13 13:58 ` ppalka 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-100187-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).