https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101134
David Malcolm <dmalcolm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dmalcolm at gcc dot gnu.org
--- Comment #11 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
FWIW the current GCC UX guidelines:
https://gcc.gnu.org/onlinedocs/gccint/Guidelines-for-Diagnostics.html
don't talk about a distinction between "possible" vs "definite" in the wording,
but it looks to me like they ought to for cases like this
...and it may already be implied by some of the stuff like "Ideally a
diagnostic should contain enough information to allow the user to make an
informed choice about whether they should care (and how to fix it), but a
balance must be drawn against overloading the user with irrelevant data.", in
that a "possible" vs "definite" distinction doesn't add much verbiage, but is
very useful in terms of clarity to the end-user, IMHO.
