[Bug c++/90960] declaring a member function with a computed typedef is confused as a data member definition

[pinskia at gcc dot gnu.org via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90960

Andrew Pinski  changed:

   What|Removed |Added

   Severity|normal  |enhancement

[Bug c++/90960] declaring a member function with a computed typedef is confused as a data member definition

[redi at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90960

Jonathan Wakely  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
   Last reconfirmed||2019-06-27
 Ever confirmed|0   |1

--- Comment #3 from Jonathan Wakely  ---
Confirming for the poor diagnostic.

[Bug c++/90960] declaring a member function with a computed typedef is confused as a data member definition

[alisdairm at me dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90960

--- Comment #2 from Alisdair Meredith  ---
I agree the second problem looks like a dupe.

It has since been pointed out to me that the first error is indeed correct, and
simply the error message is less than helpful:

[temp.spec]p8 of C++17 says:
"If a function declaration acquired its function type through a dependent type
(17.6.2.1) without using the syntactic form of a function declarator, the
program is ill-formed."

I believe this constraint is new to C++17, but so are exception specifications
in the type system that I rely on, so this bug report could be safely closed,
or treated simply as a feature request for a clearer diagnostic message that
members of dependent type can never be function declarations.

[Bug c++/90960] declaring a member function with a computed typedef is confused as a data member definition

[mpolacek at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90960

Marek Polacek  changed:

   What|Removed |Added

 CC||mpolacek at gcc dot gnu.org

--- Comment #1 from Marek Polacek  ---
The second problem is, I think, essentially a dup of 90731.