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++/101243] Coroutine lambda capture is destroyed twice
Date: Thu, 26 Aug 2021 11:49:32 +0000 [thread overview]
Message-ID: <bug-101243-4-OlO0hXf7O5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101243-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101243
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Nathan Sidwell from comment #3)
> pr.cc:71:22: error: use of deleted function 'FOO::FOO(const FOO&)'
> pr.cc:59:3: note: declared here
Maybe I'm missing the point of the code, but this is expected, isn't it?
std::function cannot store move-only callables, it requires them to be
copyable.
next prev parent reply other threads:[~2021-08-26 11:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-28 13:37 [Bug c++/101243] New: " victor.burckel at gmail dot com
2021-06-28 13:37 ` [Bug c++/101243] " victor.burckel at gmail dot com
2021-06-28 18:57 ` iains at gcc dot gnu.org
2021-08-26 11:39 ` nathan at gcc dot gnu.org
2021-08-26 11:49 ` redi at gcc dot gnu.org [this message]
2021-08-26 23:14 ` redi at gcc dot gnu.org
2021-10-01 20:37 ` iains 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-101243-4-OlO0hXf7O5@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).