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 c++/94197] __is_constructible gives an access error Date: Mon, 16 Mar 2020 17:11:11 +0000 [thread overview] Message-ID: <bug-94197-4-83ovHOFoar@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94197-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94197 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2020-03-16 Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> --- Reduced: template<typename T> T&& declval() noexcept; template<bool B> struct bool_constant { static constexpr bool value = B; using type = bool_constant; }; using true_type = bool_constant<true>; using false_type = bool_constant<false>; template<bool, typename T, typename Arg> struct __is_nt_constructible_impl : public false_type { }; template<typename T, typename Arg> struct __is_nt_constructible_impl<true, T, Arg> : public bool_constant<noexcept(static_cast<T>(declval<Arg>()))> { }; template<typename T, typename Arg> using __is_nothrow_constructible_impl = __is_nt_constructible_impl<__is_constructible(T, Arg), T, Arg>; template<typename T> struct __is_nothrow_copy_constructible_impl : public __is_nothrow_constructible_impl<T, const T&> #ifdef FIX ::type #endif { }; template<typename T> struct is_nothrow_copy_constructible : public __is_nothrow_copy_constructible_impl<T> #ifndef FIX ::type #endif { }; struct NType { NType(); private: NType(const NType&); }; static_assert( !is_nothrow_copy_constructible<NType>::value, "" );
next prev parent reply other threads:[~2020-03-16 17:11 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-16 16:06 [Bug c++/94197] New: " redi at gcc dot gnu.org 2020-03-16 17:11 ` redi at gcc dot gnu.org [this message] 2020-03-16 17:36 ` [Bug c++/94197] " ville.voutilainen at gmail dot com 2020-03-16 21:44 ` redi at gcc dot gnu.org 2020-03-17 15:03 ` cvs-commit at gcc dot gnu.org 2021-09-30 15:01 ` ppalka 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-94197-4-83ovHOFoar@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).