public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "s.murthy at outlook dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/115656] [11/12/13/14/15 Regression] Templated ctor use rejected in non-deduced context if class template has template template parameter Date: Wed, 26 Jun 2024 19:24:33 +0000 [thread overview] Message-ID: <bug-115656-4-xPqGp34lHP@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-115656-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115656 --- Comment #6 from Sean Murthy <s.murthy at outlook dot com> --- Additional info, just in case it helps. Either of the following changes to the repro causes the reported error to disappear (not saying that either change is universally acceptable, that is, they are not workarounds). 1. In class A, unconstrain the type parameter of template template parameter V, and make no other changes anywhere else. ``` template<std::unsigned_integral U = unsigned, template <class> class V = dv > ``` 2. In class A, constrain the type parameter of template template parameter V using type_traits *and* unconstrain the type parameter of class template dv: ``` template<typename> class dv; template<std::unsigned_integral U = unsigned, template <typename T> requires std::is_unsigned_v<T> class V = dv > ``` Furthermore, constraining the type parameter of class template dv using type_traits instead of concepts causes *CTAD fail* for class A and non-CTAD fail for class B (which is odd because the change has nothing to do with class B). And these failures go back to GCC 10.1. Assuming purely C++20 issue, this particular manifestation does not appear to be regression. See: https://sigcpp.godbolt.org/z/79oEaG1vo
prev parent reply other threads:[~2024-06-26 19:24 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-06-26 1:42 [Bug c++/115656] New: " s.murthy at outlook dot com 2024-06-26 1:48 ` [Bug c++/115656] " s.murthy at outlook dot com 2024-06-26 3:57 ` s.murthy at outlook dot com 2024-06-26 4:13 ` s.murthy at outlook dot com 2024-06-26 4:26 ` s.murthy at outlook dot com 2024-06-26 7:31 ` [Bug c++/115656] [11/12/13/14/15 Regression] " rguenth at gcc dot gnu.org 2024-06-26 14:00 ` mpolacek at gcc dot gnu.org 2024-06-26 19:24 ` s.murthy at outlook dot com [this message]
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-115656-4-xPqGp34lHP@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).