[Bug c++/100084] using enum lookup isn't type-only

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

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

Andrew Pinski  changed:

   What|Removed |Added

 CC||luizfvalle at pm dot me

--- Comment #4 from Andrew Pinski  ---
*** Bug 103824 has been marked as a duplicate of this bug. ***

[Bug c++/100084] using enum lookup isn't type-only

[hewillk at gmail dot com via Gcc-bugs]

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

康桓瑋  changed:

   What|Removed |Added

 CC||hewillk at gmail dot com

--- Comment #3 from 康桓瑋  ---
Here is a weird case that I think should be accepted:

enum e { e };
using enum e;

gcc rejects with:

:2:12: error: 'e' is not a type
2 | using enum e;
  |^

[Bug c++/100084] using enum lookup isn't type-only

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

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

Marek Polacek  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever confirmed|0   |1
 CC||mpolacek at gcc dot gnu.org
   Keywords||accepts-invalid,
   ||rejects-valid
   Last reconfirmed||2021-04-14

--- Comment #2 from Marek Polacek  ---
Confirmed.

[Bug c++/100084] using enum lookup isn't type-only

[barry.revzin at gmail dot com via Gcc-bugs]

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

--- Comment #1 from Barry Revzin  ---
Also gcc accepts:

namespace A { enum A {}; };
using namespace A;
using enum A::A;

Which, apparently, this one should actually be ambiguous.