public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ppalka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/108393] circular concept false-positive Date: Fri, 13 Jan 2023 16:28:05 +0000 [thread overview] Message-ID: <bug-108393-4-o7LQUJVopk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108393-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108393 Patrick Palka <ppalka at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://gcc.gnu.org/bugzill | |a/show_bug.cgi?id=99599 CC| |ppalka at gcc dot gnu.org --- Comment #3 from Patrick Palka <ppalka at gcc dot gnu.org> --- IIUC this is a consequence of CWG2369, which made us check check constraints before checking non-dependent conversions, and which AFAIK only GCC implements. It can be worked around by encoding the conversion to unreachable_sentinel_t as an additional constraint guarding the real constraint: template<std::convertible_to<unreachable_sentinel_t> T, C _Iter> friend constexpr bool operator==(T, const _Iter&) noexcept; See also PR99599
next prev parent reply other threads:[~2023-01-13 16:28 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-13 13:58 [Bug c++/108393] New: " nikolasklauser at berlin dot de 2023-01-13 16:09 ` [Bug c++/108393] " redi at gcc dot gnu.org 2023-01-13 16:15 ` redi at gcc dot gnu.org 2023-01-13 16:28 ` ppalka at gcc dot gnu.org [this message] 2023-01-27 17:02 ` pinskia at gcc dot gnu.org 2023-05-19 3:34 ` pinskia at gcc dot gnu.org 2024-03-09 15:37 ` 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-108393-4-o7LQUJVopk@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).