https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108965
--- Comment #8 from Christopher Friedt <chrisfriedt at gmail dot com> --- My code is clearly valid C++ according to g++ :-) Thanks for your help in any case. On Tue, Feb 28, 2023, 7:38 AM redi at gcc dot gnu.org < gcc-bugzi...@gcc.gnu.org> wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108965 > > --- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> --- > (In reply to Christopher Friedt from comment #6) > > It's supported OOTB in `clang++` but fails in `g++`. > > Nobody is disputing that, but Clang supports lots of things that aren't > valid > in C++ and aren't supported by G++, and G++ supports things that aren't > valid > in C++ and aren't supported by Clang. That's not a bug. > > > The example above is the simplest example that illustrates the issue. > > Yes, and it's not valid C++. > > > I am not being abusive, but it certainly did feel like gaslighting to > read > > "you're doing it wrong" / close invalid without any consideration. > > I commented explaining that it's not in the C++ standard, and followed up > in > the github issue where the real bug is. That's hardly "without > consideration". > I've shown how to fix your C++ code to make it valid in C++11, and pointed > out > a problem in your C code using _Generic. I didn't have to do any of that, > and I > certainly won't bother doing so again. > > -- > You are receiving this mail because: > You reported the bug.
