dcoughlin added a comment. I'm curious about the use case for this, since I don't think it ever makes sense to run all the alpha checks at once. These checks are typically a work in progress (they're not finished yet) and often have false positives that haven't been fixed yet. Often they don't handle all facets of the language and can crash on unhandled constructs. While it makes sense to enable a specific alpha check (or even a set of related alpha checks) when developing these checks or when evaluating whether they are ready to graduate into non-alpha it seems to me that running all of them isn't useful, ever.
There is a real cost to this. People often don't know what 'alpha' means and so when they run all the alpha checks they get an incorrect perspective of the quality of the analyzer. They don't realize that the alpha checks are purely used as a mechanism to support in-tree incremental development. Without a strong rationale for this flag, I would be very opposed it since (as we have seen in the past) it leads to a poor user experience. Repository: rCTE Clang Tools Extra https://reviews.llvm.org/D46159 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
