public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/95915] [10/11 Regression] std::variant doesn't like types with a defaulted virtual destructor Date: Sun, 28 Jun 2020 21:37:51 +0000 [thread overview] Message-ID: <bug-95915-4-dzJ1u7Jop3@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95915-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95915 --- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Ville Voutilainen <ville@gcc.gnu.org>: https://gcc.gnu.org/g:24b54628cfa95194a8de4071c28cb56e6e81c08e commit r11-1698-g24b54628cfa95194a8de4071c28cb56e6e81c08e Author: Ville Voutilainen <ville.voutilainen@gmail.com> Date: Mon Jun 29 00:36:38 2020 +0300 PR libstdc++/95915 PR libstdc++/95915 * include/std/type_traits (is_literal_type, is_literal_type_v): Deprecate in C++17. * include/std/variant (_Uninitialized): Adjust the condition and the comment. * testsuite/20_util/is_literal_type/deprecated-1z.cc: New. * testsuite/20_util/is_literal_type/requirements/explicit_instantiation.cc: Adjust. * testsuite/20_util/is_literal_type/requirements/typedefs.cc: Likewise. * testsuite/20_util/is_literal_type/value.cc: Likewise. * testsuite/20_util/optional/constexpr/nullopt.cc: Use __is_literal_type directly. * testsuite/20_util/optional/nullopt.cc: Likewise. * testsuite/20_util/variable_templates_for_traits.cc: Adjust. * testsuite/20_util/variant/95915.cc: New. * testsuite/20_util/variant/compile.cc: Add new test. * testsuite/experimental/optional/constexpr/nullopt.cc: Use __is_literal_type directly. * testsuite/experimental/optional/nullopt.cc: Likewise. * testsuite/experimental/type_traits/value.cc: Adjust. * testsuite/util/testsuite_common_types.h: Use __is_literal_type directly.
next prev parent reply other threads:[~2020-06-28 21:37 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-26 14:40 [Bug libstdc++/95915] New: " ville.voutilainen at gmail dot com 2020-06-26 14:41 ` [Bug libstdc++/95915] " ville.voutilainen at gmail dot com 2020-06-26 18:19 ` [Bug libstdc++/95915] [10/11 Regression] " redi at gcc dot gnu.org 2020-06-27 18:06 ` ville.voutilainen at gmail dot com 2020-06-28 21:37 ` cvs-commit at gcc dot gnu.org [this message] 2020-06-29 11:04 ` cvs-commit at gcc dot gnu.org 2020-06-29 11:05 ` ville.voutilainen at gmail dot com
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-95915-4-dzJ1u7Jop3@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).