public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "danakj at orodu dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/99599] [11/12/13/14 Regression] Concepts requirement falsely reporting cyclic dependency, breaks tag_invoke pattern Date: Wed, 07 Jun 2023 20:03:53 +0000 [thread overview] Message-ID: <bug-99599-4-GJG4LkshLe@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99599-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99599 --- Comment #16 from danakj at orodu dot net --- Well for anyone who hits the same issue, it appears that GCC _does_ follow Clang and MSVC in not considering the overload and chasing through the concept resolution if the non-concept types are templates and do not match the caller's arguments. So you need to do: 1) For non-GCC just use: template<fooable T> auto invoke_tag(bar_tag, T it); 2) For GCC non-template type bar_tag use: template<std::same_as<bar_tag> T, fooable U> auto invoke_tag(T, U it); 3) For GCC template type bar_tag, back to 1) template<class P, fooable T> auto invoke_tag(bar_tag<P>, T it); Note also that 2) uses same_as, not convertible_to as in Comment #6, otherwise you can get ambiguous overload resolution if multiple types convert to one, which does not occur in Clang/MSVC with the regular type parameter. This _does_ again result in more code that will compile in Clang/MSVC than in GCC, as it prevents conversions from types that don't have an overload. The macros to do this get rather exciting, if that's of interest to someone in the future: https://github.com/chromium/subspace/pull/253/commits/719500c4d2cbfcfd238d7ee3c5b3d371f40e46c1
next prev parent reply other threads:[~2023-06-07 20:03 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-15 13:24 [Bug c++/99599] New: Concepts requirement falsely reporting recursion, " the_gamester28 at msn dot com 2021-03-15 13:49 ` [Bug c++/99599] [11 Regression] Concepts requirement falsely reporting cyclic dependency, " rguenth at gcc dot gnu.org 2021-03-15 14:20 ` redi at gcc dot gnu.org 2021-04-01 22:04 ` jason at gcc dot gnu.org 2021-04-02 12:47 ` gcc-bugs at marehr dot dialup.fu-berlin.de 2021-04-05 19:49 ` the_gamester28 at msn dot com 2021-04-27 11:40 ` [Bug c++/99599] [11/12 " jakub at gcc dot gnu.org 2021-05-01 17:38 ` ppalka at gcc dot gnu.org 2021-07-28 7:06 ` rguenth at gcc dot gnu.org 2021-08-25 14:44 ` ppalka at gcc dot gnu.org 2022-04-21 7:48 ` rguenth at gcc dot gnu.org 2022-08-08 15:06 ` [Bug c++/99599] [11/12/13 " ppalka at gcc dot gnu.org 2022-10-27 12:42 ` ppalka at gcc dot gnu.org 2023-04-04 5:33 ` catsith at me dot com 2023-05-29 10:04 ` [Bug c++/99599] [11/12/13/14 " jakub at gcc dot gnu.org 2023-06-07 18:25 ` danakj at orodu dot net 2023-06-07 18:41 ` danakj at orodu dot net 2023-06-07 20:03 ` danakj at orodu dot net [this message] 2023-08-01 18:16 ` ppalka at gcc dot gnu.org 2023-09-08 16:03 ` cvs-commit at gcc dot gnu.org 2024-02-02 18:02 ` [Bug c++/99599] [11/12/13 " ppalka at gcc dot gnu.org 2024-03-09 15:37 ` ppalka at gcc dot gnu.org 2024-03-21 21:40 ` redi at gcc dot gnu.org 2024-03-21 21:43 ` redi at gcc dot gnu.org 2024-03-22 14:08 ` ppalka at gcc dot gnu.org 2024-03-22 15:58 ` redi at gcc dot gnu.org 2024-03-27 23:16 ` redi at gcc dot gnu.org 2024-03-27 23:18 ` 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-99599-4-GJG4LkshLe@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).