can't we just reword the one warning where there is an ambiguity to
avoid the confusion, rather than creating such an earthquake, which
as Arno says, really has zero advantages to Ada programmers, and clear
disadvantages .. to me [enabled by default] is already awfully long!
Well, since the Ada part has been rejected I think we just need to
consider this from the non-Ada perspective. And IMO there's zero
chance that each new warning will be audited for whether the
"[enabled by default]" will be unambiguous. The fact that this
particular warning caused confusion and someone actually reported
it doesn't mean that there are no other warnings like that. E.g.:
-fprefetch-loop-arrays is not supported with -Os [enabled by default]
could also be misunderstood, especially if working on an existing codebase
with an existing makefile. And the effect for:
pragma simd ignored because -fcilkplus is not enabled [enabled by default]
is a bit unfortunate. Those were just two examples -- I'm sure I could
pick more.