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++/71579] type_traits miss checks for type completeness in some traits Date: Fri, 02 Sep 2022 10:48:33 +0000 [thread overview] Message-ID: <bug-71579-4-bqFeRbahyI@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-71579-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71579 --- Comment #23 from Jonathan Wakely <redi at gcc dot gnu.org> --- Yes, that's my reading of it. I need to check what other compilers do for __has_virtual_destructor and check the docs. Maybe libstdc++ should only use it for class types.
next prev parent reply other threads:[~2022-09-02 10:48 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-71579-4@http.gcc.gnu.org/bugzilla/> 2020-05-07 11:56 ` jakub at gcc dot gnu.org 2020-06-09 14:18 ` kuzniar95 at o2 dot pl 2020-07-23 6:52 ` rguenth at gcc dot gnu.org 2020-07-23 11:30 ` redi at gcc dot gnu.org 2020-08-19 11:25 ` cvs-commit at gcc dot gnu.org 2020-09-24 17:51 ` cvs-commit at gcc dot gnu.org 2022-09-01 21:58 ` redi at gcc dot gnu.org 2022-09-01 22:00 ` redi at gcc dot gnu.org 2022-09-02 6:03 ` antoshkka at gmail dot com 2022-09-02 10:48 ` redi at gcc dot gnu.org [this message] 2022-09-05 17:14 ` redi at gcc dot gnu.org 2023-05-26 18:01 ` 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-71579-4-bqFeRbahyI@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).