https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82478
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82478
Andrew Pinski changed:
What|Removed |Added
Known to fail||10.1.0, 11.1.0
--- Comment #7 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82478
Alexander Zaitsev changed:
What|Removed |Added
CC||zamazan4ik at tut dot by
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82478
--- Comment #5 from Corey Tabaka ---
>From what I can tell the standard is not very explicit about the access rules
in the argument list of a partial specialization specifically. However, there
are examples in the spec that demonstrate friend
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82478
--- Comment #4 from Corey Tabaka ---
Ah, you are right. Late night mixup...
The outer class friend should work though, correct?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82478
--- Comment #3 from Jonathan Wakely ---
The template argument list of ::HasPrivate is
not a base-specifier.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82478
--- Comment #2 from Corey Tabaka ---
From section 11.3.2 of the C++14 draft spec:
"Declaring a class to be a friend implies that the names of private and
protected members from the class granting friendship can be accessed in the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82478
--- Comment #1 from Jonathan Wakely ---
Reduced:
struct true_type { static const bool value = true; };
struct false_type { static const bool value = false; };
template
using void_t = void;
template
struct