public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hewillk at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/103951] [C++2b] string_view range constructor, "exception specification ... depends on itself" Date: Sun, 09 Jan 2022 15:54:10 +0000 [thread overview] Message-ID: <bug-103951-4-H8lZw7BzWy@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103951-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103951 --- Comment #2 from 康桓瑋 <hewillk at gmail dot com> --- Here is the reduced version without the header: template<class T> T&& declval() noexcept; struct true_type { static constexpr bool value = true; }; template<typename _From, typename _To> class is_convertible { template<typename _To1> static void __test_aux(_To1) noexcept; template<typename _From1, typename _To1, typename = decltype(__test_aux<_To1>(declval<_From1>()))> static true_type __test(int); public: static constexpr bool value = decltype(__test<_From, _To>(0))::value; }; template<typename _Tp> void __decay_copy(_Tp) noexcept(is_convertible<_Tp, _Tp>::value); template<class _Tp> concept range = requires(_Tp& __t) { __decay_copy(__t.begin()); }; struct string_view { template<range R> string_view(R&&); }; struct Iter { Iter(string_view); Iter begin() const { return *this; } }; https://godbolt.org/z/nrcq84dno
next prev parent reply other threads:[~2022-01-09 15:54 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-09 10:23 [Bug libstdc++/103951] New: " iamsupermouse at mail dot ru 2022-01-09 10:58 ` [Bug libstdc++/103951] " hewillk at gmail dot com 2022-01-09 15:54 ` hewillk at gmail dot com [this message] 2022-01-10 9:39 ` redi 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-103951-4-H8lZw7BzWy@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).