public inbox for libstdc++-cvs@sourceware.org help / color / mirror / Atom feed
From: Jonathan Wakely <redi@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org Subject: [gcc r11-9927] libstdc++: Remove workaround for FE bug in std::tuple [PR96592] Date: Thu, 21 Apr 2022 15:34:00 +0000 (GMT) [thread overview] Message-ID: <20220421153400.C78B93842585@sourceware.org> (raw) https://gcc.gnu.org/g:d65b274f1f44c59382b7dad7759cfaf3c8397cf8 commit r11-9927-gd65b274f1f44c59382b7dad7759cfaf3c8397cf8 Author: Jonathan Wakely <jwakely@redhat.com> Date: Fri Nov 26 17:46:47 2021 +0000 libstdc++: Remove workaround for FE bug in std::tuple [PR96592] The FE bug was fixed, so we don't need this workaround now. libstdc++-v3/ChangeLog: PR libstdc++/96592 * include/std/tuple (tuple::is_constructible): Remove. (cherry picked from commit 76c6be48b7841524974754f8ea7533b82c7de77e) Diff: --- libstdc++-v3/include/std/tuple | 4 ---- 1 file changed, 4 deletions(-) diff --git a/libstdc++-v3/include/std/tuple b/libstdc++-v3/include/std/tuple index dcf30bd9a8d..63bd68fbe43 100644 --- a/libstdc++-v3/include/std/tuple +++ b/libstdc++-v3/include/std/tuple @@ -553,10 +553,6 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION template<bool, typename... _Types> struct _TupleConstraints { - template<typename _Tp, typename _Up> // Workaround for PR 96592 - using is_constructible - = __bool_constant<__is_constructible(_Tp, _Up)>; - // Constraint for a non-explicit constructor. // True iff each Ti in _Types... can be constructed from Ui in _UTypes... // and every Ui is implicitly convertible to Ti.
reply other threads:[~2022-04-21 15:34 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220421153400.C78B93842585@sourceware.org \ --to=redi@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ --cc=libstdc++-cvs@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).