https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86186
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> --- If you want to suggest that GCC should have a new warning, then say that. Don't past valid code and incorrectly claim that clang rejects it, or provide a link to a bug in libc++ which is completely irrelevant to GCC (we don't care that libc++ had a bug and then fixed it, that's not a GCC problem!) I've spent hours and hours processing your bug reports this week, and far too many of them have been confusing, poorly described, or just plain wrong. SOme have been real bugs, so thank you for that, but you're also causing me to waste a lot of time.
