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++/100476] coroutines: questionable handling of void get_return_object
Date: Fri, 07 May 2021 19:20:24 +0000	[thread overview]
Message-ID: <bug-100476-4-uVCYS9hKGd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100476-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100476

--- Comment #1 from Iain Sandoe <iains at gcc dot gnu.org> ---
I am by no means an expert at reading standardese - and it might be that I'm
not alone, (library writers might have made the same assumption) but it seems
to me that:

http://eel.is/c++draft/dcl.fct.def.coroutine#7

Doe not make any specification about what get_­return_­object() returns, only
that it is possible to use it either (a) to initialise the return value
directly or (b) to construct a return value object from it.

  reply	other threads:[~2021-05-07 19:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-07 15:59 [Bug c++/100476] New: " jason at gcc dot gnu.org
2021-05-07 19:20 ` iains at gcc dot gnu.org [this message]
2021-05-07 19:54 ` [Bug c++/100476] " jason at gcc dot gnu.org
2021-05-07 19:59 ` jason at gcc dot gnu.org
2021-05-07 20:07 ` iains at gcc dot gnu.org
2021-05-07 20:12 ` iains at gcc dot gnu.org
2023-01-05  7:47 ` iains at gcc dot gnu.org
2024-06-29  2:05 ` iains at gcc dot gnu.org
2024-08-17 15:25 ` iains at gcc dot gnu.org
2024-08-24 18:54 ` cvs-commit at gcc dot gnu.org
2024-08-27  7:53 ` 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-100476-4-uVCYS9hKGd@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).