NoQ added a comment. We (me, Valeriy, Devin)'ve just been talking about this and mostly of agreed that `core.CallAndMessage` should ideally be removed (at least as a `Checkers.td` entity) and individual checks moved to the relevant package (null dereference, use of uninitialized value, etc.). It won't hurt backwards compatibility too much because so far there was no reasonable outcome that one might expect from disabling `core.CallAndMessage`, given that it's a weird mix of completely unrelated checks. The benefit is that disabling, say, null dereference checker will actually disable all null dereference warnings (as opposed to having to additionally disable the ones that come from `CallAndMessage`).
Also a regular reminder that we wouldn't have had this conversation if we had hashtags instead of packages (#CallAndMessage #NullDereference #C++ #AllPlatforms #UndefinedBehavior #SecurityCritical #PathSensitive #Stable #2012). Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D77866/new/ https://reviews.llvm.org/D77866 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
