public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redbeard0531 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/99021] New: coroutine_handle<_Promise>::from_address() should be noexcept Date: Tue, 09 Feb 2021 10:27:28 +0000 [thread overview] Message-ID: <bug-99021-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99021 Bug ID: 99021 Summary: coroutine_handle<_Promise>::from_address() should be noexcept Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: redbeard0531 at gmail dot com Target Milestone: --- While it isn't required by the standard, it seems odd that coroutine_handle<void>::from_address() is noexcept while the non-specialized version isn't when they are the same code. This would also help with clang/libstdc++ compatibility because they currently check for noexcept of from_address() as part of validating https://eel.is/c++draft/dcl.fct.def.coroutine#15 (I'll be filing a bug with them about that shortly since that is leaking an internal compiler implementation detail).
next reply other threads:[~2021-02-09 10:27 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-09 10:27 redbeard0531 at gmail dot com [this message] 2021-02-09 10:42 ` [Bug libstdc++/99021] " redbeard0531 at gmail dot com 2021-02-09 12:32 ` cvs-commit at gcc dot gnu.org 2021-02-09 13:42 ` redbeard0531 at gmail dot com 2021-02-09 14:26 ` cvs-commit at gcc dot gnu.org 2021-02-09 14:44 ` redi 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-99021-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).