public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nikolasklauser at berlin dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/106611] std::is_nothrow_copy_constructible returns wrong result
Date: Sat, 13 Aug 2022 21:23:08 +0000 [thread overview]
Message-ID: <bug-106611-4-GyQ0Ua4Cg0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106611-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106611
--- Comment #2 from Nikolas Klauser <nikolasklauser at berlin dot de> ---
(In reply to Jonathan Wakely from comment #1)
> The noexcept specifier is wrong, but is ignored. The implicitly defined copy
> constructor is noexcept, so the trait gives the right answer.
static_assert(!noexcept(std::declval<const CopyConstructible&>())));
is fine. So one of them must be wrong.
next prev parent reply other threads:[~2022-08-13 21:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-13 21:02 [Bug libstdc++/106611] New: " nikolasklauser at berlin dot de
2022-08-13 21:14 ` [Bug libstdc++/106611] " redi at gcc dot gnu.org
2022-08-13 21:23 ` nikolasklauser at berlin dot de [this message]
2022-08-14 0:57 ` nikolasklauser at berlin dot de
2022-12-07 0:25 ` nikolasklauser at berlin dot de
2023-01-06 11:10 ` de34 at live dot cn
2023-08-03 23:29 ` nikolasklauser at berlin dot de
2023-08-04 2:28 ` de34 at live dot cn
2023-08-07 1:07 ` de34 at live dot cn
2023-08-08 21:19 ` arthur.j.odwyer at gmail dot com
2023-08-08 21:24 ` pinskia at gcc dot gnu.org
2023-08-08 21:44 ` arthur.j.odwyer at gmail dot com
2023-08-08 21:45 ` pinskia at gcc dot gnu.org
2023-08-09 2:52 ` de34 at live dot cn
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-106611-4-GyQ0Ua4Cg0@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).