http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48948
Johannes Schaub <schaub.johannes at googlemail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |schaub.johannes at
| |googlemail dot com
--- Comment #1 from Johannes Schaub <schaub.johannes at googlemail dot com>
2011-05-10 14:49:18 UTC ---
(In reply to comment #0)
> gcc 4.7.0 20110507 (experimental) in C++0x mode rejects the following code at
> the line marked with #:
>
> //---
> struct B {
> friend constexpr int f(B) { return 0; } // #
> };
> //---
>
> "error: invalid type for parameter 1 of constexpr function 'constexpr int
> f(B)'"
>
> This code should be accepted.
>
> The same problem occurs with friend operators, like this case
>
> friend constexpr int operator+(B) { return 0; }
>
> within B resulting in:
>
> "error: invalid type for parameter 1 of constexpr function 'constexpr int
> operator+(B)'"
>
Well, class "B" is incomplete in the parameter type list of f. The spec allows
B to be incomplete for that parameter type (8.3.5p9), but it doesn't say
anything what that means for determining whether or not the parameter has
literal class type (several of the bullets of 3.9p10 require a complete class
type to be checked). I don't know whether an implementation is supposed to
reject the code, or supposed to wait until B is complete. Same would apply for
non-static member functions.
Any hints?
