https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80151
--- Comment #12 from Jonathan Wakely <redi at gcc dot gnu.org> --- If we had a clear description of the warning (when it should/shouldn't warn, whether it should be on or off by default, whether it should be part of an existing warning, or the -Wstring-conversion one propose here, etc) then we wouldn't need to guess. Vague requests for new warnings are not actionable and are likely to be ignored without a clear description of the desired semantics.
