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 r13-2344] libstdc++: Remove FIXME for ICE with remove_cvref_t in requires-expression Date: Thu, 1 Sep 2022 14:48:44 +0000 (GMT) [thread overview] Message-ID: <20220901144844.8B1483858D1E@sourceware.org> (raw) https://gcc.gnu.org/g:37ff51a98583e63fb9afe83cf9f4351760149028 commit r13-2344-g37ff51a98583e63fb9afe83cf9f4351760149028 Author: Jonathan Wakely <jwakely@redhat.com> Date: Thu Sep 1 11:52:52 2022 +0100 libstdc++: Remove FIXME for ICE with remove_cvref_t in requires-expression PR c++/99968 is fixed since GCC 12.1 so we can remove the workaround. libstdc++-v3/ChangeLog: * include/std/type_traits (is_scoped_enum): Remove workaround. Diff: --- libstdc++-v3/include/std/type_traits | 11 +---------- 1 file changed, 1 insertion(+), 10 deletions(-) diff --git a/libstdc++-v3/include/std/type_traits b/libstdc++-v3/include/std/type_traits index 5984442c0aa..5b8314f24fd 100644 --- a/libstdc++-v3/include/std/type_traits +++ b/libstdc++-v3/include/std/type_traits @@ -3534,20 +3534,11 @@ template<typename _Ret, typename _Fn, typename... _Args> template<typename _Tp> requires __is_enum(_Tp) - && requires(_Tp __t) { __t = __t; } // fails if incomplete + && requires(remove_cv_t<_Tp> __t) { __t = __t; } // fails if incomplete struct is_scoped_enum<_Tp> : bool_constant<!requires(_Tp __t, void(*__f)(int)) { __f(__t); }> { }; - // FIXME remove this partial specialization and use remove_cv_t<_Tp> above - // when PR c++/99968 is fixed. - template<typename _Tp> - requires __is_enum(_Tp) - && requires(_Tp __t) { __t = __t; } // fails if incomplete - struct is_scoped_enum<const _Tp> - : bool_constant<!requires(_Tp __t, void(*__f)(int)) { __f(__t); }> - { }; - /// @ingroup variable_templates /// @since C++23 template<typename _Tp>
reply other threads:[~2022-09-01 14:48 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=20220901144844.8B1483858D1E@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).