public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vin.piquet at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/114695] Template argument deduction and defaulted template template parameters
Date: Fri, 12 Apr 2024 09:24:55 +0000 [thread overview]
Message-ID: <bug-114695-4-Y5A4r3kyn3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114695-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114695
--- Comment #3 from Vincent Piquet <vin.piquet at gmail dot com> ---
Interesting. Now I think the issue may actually be caused by pack expansion on
the call site. The issue also happens when Foo only has one base class, albeit
with a different error that at least has concise types on both sides.
==== test.cpp ====
template <typename X> struct Bar {
void accept(X value) { }
};
template <typename...> struct Foo;
template <typename... Ts>
struct Foo<Bar<Ts>...> : Bar<Ts>... {
template <typename T, template <typename> typename B = Bar>
constexpr static B<T>* slice_by_type(B<T>* self) {
return self;
}
template <typename... Us>
void accept(Us... values) {
(slice_by_type<Us>(this)->accept(values), ...);
}
};
int main() {
Foo<Bar<float>> foo;
foo.accept(3.14f);
}
==== test.cpp ====
==== GCC 13.2 ====
test.cpp: In instantiation of 'void Foo<Bar<Ts>...>::accept(Us ...) [with Us =
{float}; Ts = {float}]':
test.cpp:22:15: required from here
test.cpp:16:27: error: no matching function for call to 'Foo<Bar<float>
>::slice_by_type<float>(Foo<Bar<float> >*)'
16 | (slice_by_type<Us>(this)->accept(values), ...);
| ~~~~~~~~~~~~~~~~~^~~~~~
test.cpp:10:28: note: candidate: 'template<class T, template<class> class B>
static constexpr B<T>* Foo<Bar<Ts>...>::slice_by_type(B<T>*) [with B = T; Ts =
{float}]'
10 | constexpr static B<T>* slice_by_type(B<T>* self) {
| ^~~~~~~~~~~~~
test.cpp:10:28: note: template argument deduction/substitution failed:
test.cpp:16:27: note: deduced conflicting types for parameter 'T' ('float'
and 'Bar<float>')
16 | (slice_by_type<Us>(this)->accept(values), ...);
| ~~~~~~~~~~~~~~~~~^~~~~~
==== GCC 13.2 ====
This may however be simplified so much that it becomes another bug. I'm unsure.
next prev parent reply other threads:[~2024-04-12 9:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-11 16:45 [Bug c++/114695] New: " vin.piquet at gmail dot com
2024-04-11 23:44 ` [Bug c++/114695] " pinskia at gcc dot gnu.org
2024-04-11 23:47 ` pinskia at gcc dot gnu.org
2024-04-12 9:24 ` vin.piquet at gmail dot com [this message]
2024-04-12 9:30 ` vin.piquet at gmail dot com
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-114695-4-Y5A4r3kyn3@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: link
Be 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).