public inbox for gcc-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 r10-9942] libstdc++: Remove unused helpers for std::variant Date: Fri, 18 Jun 2021 13:11:18 +0000 (GMT) [thread overview] Message-ID: <20210618131118.185803860C32@sourceware.org> (raw) https://gcc.gnu.org/g:49b41ca3d010c7e394e3d71bf2f71c556cee70f3 commit r10-9942-g49b41ca3d010c7e394e3d71bf2f71c556cee70f3 Author: Jonathan Wakely <jwakely@redhat.com> Date: Fri Jun 18 14:07:57 2021 +0100 libstdc++: Remove unused helpers for std::variant The r10-9937-g8ad4d9b46944db1be6f1b216b5b8e74bd9f66937 backport brought these helpers from the gcc-11 branch, but they aren't needed for the std::variant implementation in the gcc-10 branch. * include/std/variant (__same_types, __check_visitor_results): Remove. Diff: --- libstdc++-v3/include/std/variant | 11 ----------- 1 file changed, 11 deletions(-) diff --git a/libstdc++-v3/include/std/variant b/libstdc++-v3/include/std/variant index 5f76d76490e..660b7fbc31c 100644 --- a/libstdc++-v3/include/std/variant +++ b/libstdc++-v3/include/std/variant @@ -1061,17 +1061,6 @@ namespace __variant using __visit_result_t = invoke_result_t<_Visitor, __get_t<0, _Variants>...>; - template<typename _Tp, typename... _Types> - constexpr inline bool __same_types = (is_same_v<_Tp, _Types> && ...); - - template <typename _Visitor, typename _Variant, size_t... _Idxs> - constexpr bool __check_visitor_results(std::index_sequence<_Idxs...>) - { - return __same_types< - invoke_result_t<_Visitor, __get_t<_Idxs, _Variant>>... - >; - } - } // namespace __variant } // namespace __detail
reply other threads:[~2021-06-18 13:11 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=20210618131118.185803860C32@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).