pfultz2 added a comment. > When something is merged into Clang trunk, the expectation is that it will be > production quality or will be worked on rapidly to get it to production > quality, which is somewhat orthogonal to getting user feedback. I don't know > that I have the full history of all of the alpha checks so my generalization > may be inaccurate, but it seems like some of these checks were accepted as a > WIP and the "progress" stopped for a long time with no one volunteering to > remove the features from the analyzer.
Some checkers work better than others, while some just need some simple fixes. Of course, no one will volunteer to fix or remove them if they aren't available to run. > That does not require clang-tidy to surface the alpha checks, correct? A good portion of users are using clang-tidy to run the static analyzer, and I would like it to be exposed to them. https://reviews.llvm.org/D46159 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
