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++/112802] New: <ranges>: _ToClosure::operator() has no constraints Date: Fri, 01 Dec 2023 03:36:34 +0000 [thread overview] Message-ID: <bug-112802-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112802 Bug ID: 112802 Summary: <ranges>: _ToClosure::operator() has no constraints Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: hewillk at gmail dot com Target Milestone: --- which means this is not SFINAE-friendly. That's not standard compliance, right? #include <ranges> #include <vector> template<class T> concept test = requires { std::ranges::to<std::vector<int>>()(T{}); }; static_assert(!test<int>); // hard error in libstdc++ https://godbolt.org/z/Tasba18Kv
next reply other threads:[~2023-12-01 3:36 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-01 3:36 hewillk at gmail dot com [this message] 2023-12-01 15:03 ` [Bug libstdc++/112802] " redi at gcc dot gnu.org 2023-12-06 20:04 ` ppalka at gcc dot gnu.org 2023-12-18 23:06 ` cvs-commit at gcc dot gnu.org 2023-12-18 23:07 ` 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-112802-4@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).