Re: constexpr keyword is unnecessary

On 2024-11-04, Lowell Gilbert <lgusenet@be-well.ilk.org> wrote:

The question of how to shut up a warning that is truly innocuous is not
part of this policy. In my own opinion, it will often require its own
policy. That is a separate topic, because it can quite reasonably vary
depending on a number of factors in the development environment, most
notably the compiler itself.

What warnings are disabled or enabled is a
team/project/department/company decision; what you don't want is lone
developers making commits which combine their code change, with an
accompanying build change that shuts up a warning that their code change
causes.

That could be allowed, if it is confined to the code (e.g with a pragma)
and a ticket is opened for that issue. The ticket will be resolved
either by adopting the suppression of the warning project-wide, or
else by removing the temporary local suppression and reworking the code.

--
TXR Programming Language: http://nongnu.org/txr
Cygnal: Cygwin Native Application Library: http://kylheku.com/cygnal
Mastodon: @Kazinator@mstdn.ca