Issue 58094
Summary make the default `misc-const-correctness` mode optional
Labels new issue
Assignees
Reporter firewave
    Thinking in the terms of #58084 the warnings from the optional `misc-const-correctnes.WarnPointersAsValues` can be considered "safe" (to be applied without any review) as the fixes apply apply to local assignments only and might not mask patterns of unintentional copies.

As the default warnings (currently) include "unsafe" (which should be reviewed) cases and also lead to a different kind of fixes it might make sense to be able to run these checks mutually exclusive.

CC @JonasToth
_______________________________________________
llvm-bugs mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

Reply via email to