public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bruck.michael at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/95540] [coroutine] coroutine_traits<> lookup for lambdas Date: Fri, 05 Jun 2020 15:38:08 +0000 [thread overview] Message-ID: <bug-95540-4-dx8HFjQUFm@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95540-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95540 --- Comment #3 from Michael Bruck <bruck.michael at gmail dot com> --- I think you misread, I was complaining about it passing the closure to the traits/constructor/allocator. But if that is what was agreed upon... Can the closure object that is being passed to the constructor and allocator be used for anything? I am asking because I got it to pass nullptr with the code below. But if there is no legitimate use it might as well always pass a nullptr. template <pt::handle_t F()> struct foo_t { static auto test() { return F(); } }; using moo = foo_t<[]() -> pt::handle_t{ co_return; }>; ... int main { moo::test(); }
next prev parent reply other threads:[~2020-06-05 15:38 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-04 17:03 [Bug c++/95540] New: " bruck.michael at gmail dot com 2020-06-04 17:24 ` [Bug c++/95540] " bruck.michael at gmail dot com 2020-06-05 7:32 ` iains at gcc dot gnu.org 2020-06-05 15:38 ` bruck.michael at gmail dot com [this message] 2020-06-05 15:54 ` iains at gcc dot gnu.org 2020-06-05 18:52 ` bruck.michael at gmail dot com 2020-06-05 19:19 ` iains at gcc dot gnu.org 2020-06-11 0:17 ` iains at gcc dot gnu.org 2020-06-11 7:40 ` bruck.michael at gmail dot com
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-95540-4-dx8HFjQUFm@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).