https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87407
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |NEW
Resolution|INVALID |---
Severity|normal |enhancement
--- Comment #10 from Jonathan Wakely <redi at gcc dot gnu.org> ---
That's not what I asked.
Anyway, see comment 3. We're not talking about what Clang does, we're asking
why it would be invalid for GCC to implement this warning. Maybe it would make
sense only for code that is not in headers (IMHO it makes sense in headers too,
which is why I asked why you want such code in headers, but I could accept
having the warning only for code outside headers).
Insisting it's stupid to warn about code in headers doesn't make it invalid to
warn about code outside headers. Please address the questions instead of just
closing it again.
