dcoughlin added a comment.

I just want to second that we really don't want to treat the analyzer-config 
options as user visible. These are useful as staging flags for analyzer 
development/testing and occasionally as customization points for IDEs/build 
systems. But they do not expose a coherent (or even intelligible) model to the 
end user. In particular, this means that we should never, ever ask (or 
recommend) that the end user set these from the command line. They are also not 
API -- we make no promises of backward compatibility.

We also do sometimes use analyzer config flags as an escape hatch that lets us 
pass a flag to both a new clang (which understands the flag) and an old flag 
(which doesn't). It would be a shame if we lost that escape hatch.


https://reviews.llvm.org/D36067



_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
  • [PATCH] D36067: [analyzer]... Devin Coughlin via Phabricator via cfe-commits

Reply via email to