public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "de34 at live dot cn" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/108974] std::barrier except completion function which is not manifestly noexcept Date: Thu, 02 Mar 2023 02:27:50 +0000 [thread overview] Message-ID: <bug-108974-4-xca9TX7vG0@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108974-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108974 Jiang An <de34 at live dot cn> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |de34 at live dot cn --- Comment #3 from Jiang An <de34 at live dot cn> --- > is_nothrow_invocable_v<CompletionFunction&> shall be true. If implementation divergence is not intendedly permitted, I don't think it makes much sense to introduce UB in this way. I guess we should either turn it into a mandating requirement: > Instantiation of barrier<CompletionFunction> is ill-formed > if is_nothrow_invocable_v<CompletionFunction&> is not true. Or relax the preconditions: > If any invocation to the completion function throws an exception, > the behavior is undefined. I've mailed to LWG Chair for this...
next prev parent reply other threads:[~2023-03-02 2:27 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-28 19:23 [Bug c++/108974] New: " oliver.rosten at googlemail dot com 2023-02-28 19:24 ` [Bug libstdc++/108974] " pinskia at gcc dot gnu.org 2023-02-28 21:16 ` redi at gcc dot gnu.org 2023-02-28 21:17 ` redi at gcc dot gnu.org 2023-03-02 2:27 ` de34 at live dot cn [this message] 2023-03-02 2:38 ` rodgertq at gcc dot gnu.org 2023-03-02 2:43 ` rodgertq at gcc dot gnu.org 2023-03-02 9:58 ` 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-108974-4-xca9TX7vG0@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).