https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99213
Bug ID: 99213
Summary: Incorrect pretty printing of local class type when
type's context contains a class template
specialization
Product: gcc
Version: 10.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: ppalka at gcc dot gnu.org
Target Milestone: ---
Consider:
template <class T>
struct A {
template <class U>
static auto f() {
struct S{};
return S{};
}
};
using type = void;
using type = decltype(A<int>::f<char>()); // A<int>::f<char>()::S
For this testcase, GCC 10/11 outputs:
<source>:11:7: error: conflicting declaration 'using type = struct
A<T>::f<char>::S'
11 | using type = decltype(A<int>::f<char>());
| ^~~~
Note that the nested class type 'S' gets pretty printed as 'A<T>::f<char>::S',
i.e. the argument for the template parameter T is missing in the
nested-name-specifier.
GCC 9 outputs:
<source>:11:7: error: conflicting declaration 'using type = struct A<T>::f()
[with U = char; T = int]::S'
11 | using type = decltype(A<int>::f<char>());
| ^~~~
Which isn't perfect either, but importantly all template arguments are shown in
the type.
