================
@@ -179,6 +179,12 @@ def CallAndMessageChecker
"Check whether the reciever in the message expression is "
"undefined",
"true", Released>,
+ CmdLineOption<
+ Boolean, "ArgPointeeInitializednessComplete",
+ "If set to true, treat a struct as initialized when all of its "
+ "members are initialized, otherwise when it has any initialized
"
+ "member (used only at ArgPointeeInitializedness)",
+ "false", Released>,
----------------
steakhal wrote:
This is not a priority for me. If things were not documented, I'd argue that
folks who have enabled/used this should expect that things may break in the
future. So renaming/restructuring the checker should be an option.
Documentation is part of the job of releasing a checker. A checker without docs
is (I'm tempted to say useless) far less useful.
That said, as this was the existing norm for this checker, I would not gate
this change with that requirement, but in the future we should think about
raising the bar even for this checker. Either way, we should not hold this PR
back much longer, and optionally revisit this if we have time. (I definitely
don't :s)
https://github.com/llvm/llvm-project/pull/164600
_______________________________________________
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
