public inbox for libstdc++-cvs@sourceware.org help / color / mirror / Atom feed
From: Giuliano Belinassi <giulianob@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org Subject: [gcc(refs/users/giulianob/heads/autopar_rebase2)] libstdc++, coroutine: Add missing constexpr markers. Date: Tue, 18 Aug 2020 00:58:44 +0000 (GMT) [thread overview] Message-ID: <20200818005844.838B73861843@sourceware.org> (raw) https://gcc.gnu.org/g:1157829f23bf56bcd08761c0368de7343284431b commit 1157829f23bf56bcd08761c0368de7343284431b Author: Iain Sandoe <iain@sandoe.co.uk> Date: Sun Jul 12 20:16:21 2020 +0100 libstdc++, coroutine: Add missing constexpr markers. The methods of the trivial awaitables are intended to be constexpr. libstdc++-v3/ChangeLog: * include/std/coroutine: Mark the methods of the trivial awaitables as constexpr. Diff: --- libstdc++-v3/include/std/coroutine | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/libstdc++-v3/include/std/coroutine b/libstdc++-v3/include/std/coroutine index b40a3bcf9cc..468d1107557 100644 --- a/libstdc++-v3/include/std/coroutine +++ b/libstdc++-v3/include/std/coroutine @@ -273,20 +273,20 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION /// [coroutine.trivial.awaitables] struct suspend_always { - bool await_ready() { return false; } + constexpr bool await_ready() const noexcept { return false; } - void await_suspend(coroutine_handle<>) {} + constexpr void await_suspend(coroutine_handle<>) const noexcept {} - void await_resume() {} + constexpr void await_resume() const noexcept {} }; struct suspend_never { - bool await_ready() { return true; } + constexpr bool await_ready() const noexcept { return true; } - void await_suspend(coroutine_handle<>) {} + constexpr void await_suspend(coroutine_handle<>) const noexcept {} - void await_resume() {} + constexpr void await_resume() const noexcept {} }; } // namespace __n4861
reply other threads:[~2020-08-18 0:58 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200818005844.838B73861843@sourceware.org \ --to=giulianob@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ --cc=libstdc++-cvs@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).