[Bug c++/68161] New: Inconsistent behaviour of unnamed field with inheritance.

[Bug c++/68161] New: Inconsistent behaviour of unnamed field with inheritance.

[gpderetta at gmail dot com]

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

            Bug ID: 68161
           Summary: Inconsistent behaviour of unnamed field with
                    inheritance.
           Product: gcc
           Version: 5.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: gpderetta at gmail dot com
  Target Milestone: ---

As an extension to C++, g++ allows the following:

struct B {
        struct { int bar; };
};

int main()
{
        B foo;
        (void)foo.bar; // ok
}

The following does not work though:

struct A {
        int bar;
};

struct B {
        struct : A {};
};

int main()
{

        B foo;
        (void)foo.bar;  // error: 'struct B' has no member named 'bar'
}

As unnamed struct fields are an extension, this is not really a bug as g++ can
do whatever it wants, but it does seems inconsistent. 

The expected behaviour is useful to inject arbitrary names as members.

[Bug c++/68161] Inconsistent behaviour of unnamed field with inheritance.

[pinskia at gcc dot gnu.org]

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |WONTFIX
   Target Milestone|---                         |12.0

--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
After r12-2627 we start to reject anonymous struct with bases so closing as
won't fix.