public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/95616] [coroutines] coroutines with potentially-throwing 'co_await promise.final_suspend()' expressions should be ill-formed Date: Tue, 16 Feb 2021 09:19:45 +0000 [thread overview] Message-ID: <bug-95616-4-LbbsST6JSK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95616-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95616 --- Comment #3 from Iain Sandoe <iains at gcc dot gnu.org> --- Created attachment 50197 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50197&action=edit Patch being tested this fixes the top-level check, but doesn't yet look at (a) operator co_await (b) the await_* functions. needs some tidying up.
next prev parent reply other threads:[~2021-02-16 9:19 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-09 18:51 [Bug c++/95616] New: " lewissbaker.opensource at gmail dot com 2020-06-09 19:00 ` [Bug c++/95616] " iains at gcc dot gnu.org 2020-07-23 6:52 ` rguenth at gcc dot gnu.org 2021-02-16 9:19 ` iains at gcc dot gnu.org [this message] 2021-03-05 16:59 ` cvs-commit at gcc dot gnu.org 2021-03-22 22:04 ` cvs-commit at gcc dot gnu.org 2021-03-24 12:45 ` 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-95616-4-LbbsST6JSK@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).