alexfh requested changes to this revision. alexfh added a comment. This revision now requires changes to proceed.
Hi Roman, Welcome to the community! As others noted, adding a separate check so similar functionally and implementation-wise to the existing one is not the best way to go here. A single check for all similar complexity limits would be a better solution. However, first I'd like to understand the specific use case you have for this check. Is there a recommendation of a certain style document to impose a complexity limit per-compound statement instead of a function? Should both limits be used? What would be the specific numbers and how should they interact with regard to nesting (e.g. should the warning be issued only on the innermost compound statement violating the rule or should it be issued on all levels)? https://reviews.llvm.org/D31252 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
