public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/114152] Wrong exception specifiers for LFTSv3 scope guard destructors Date: Wed, 28 Feb 2024 14:50:40 +0000 [thread overview] Message-ID: <bug-114152-4-OmV9jwTpO1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114152-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114152 --- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> --- I can take care of it this time, since I think I can figure out how to fix it just from your detailed report :-) and I've already written a testcase: // { dg-do compile { target c++20 } } // PR libstdc++/114152 // Wrong exception specifiers for LFTSv3 scope guard destructors #include <experimental/scope> using namespace std::experimental; struct F { void operator()() noexcept(false); }; static_assert( noexcept(std::declval<scope_exit<F>&>().~scope_exit()) ); static_assert( noexcept(std::declval<scope_fail<F>&>().~scope_fail()) ); static_assert( ! noexcept(std::declval<scope_success<F>&>().~scope_success()) ); struct G { void operator()() noexcept(true); }; static_assert( noexcept(std::declval<scope_exit<G>&>().~scope_exit()) ); static_assert( noexcept(std::declval<scope_fail<G>&>().~scope_fail()) ); static_assert( noexcept(std::declval<scope_success<G>&>().~scope_success()) );
next prev parent reply other threads:[~2024-02-28 14:50 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-28 14:17 [Bug libstdc++/114152] New: " victor at westerhu dot is 2024-02-28 14:40 ` [Bug libstdc++/114152] " redi at gcc dot gnu.org 2024-02-28 14:42 ` victor at westerhu dot is 2024-02-28 14:47 ` redi at gcc dot gnu.org 2024-02-28 14:50 ` redi at gcc dot gnu.org [this message] 2024-02-28 14:51 ` cvs-commit at gcc dot gnu.org 2024-03-01 10:52 ` cvs-commit at gcc dot gnu.org 2024-03-01 10:53 ` 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-114152-4-OmV9jwTpO1@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).