alexfh added a comment. In https://reviews.llvm.org/D40671#945158, @xgsa wrote:
> In https://reviews.llvm.org/D40671#944906, @alexfh wrote: > > > BTW, how will this feature interact with cpplint.py's way of handling > > specific NOLINT directives that use different lint rule names, which > > sometimes refer to the same rule (e.g. `// NOLINT(runtime/explicit)` > > suppresses the `runtime/explicit` cpplint rule that enforces the same style > > rule as the google-runtime-explicit check)? > > > This feature accepts only full check names. How are unknown check names handled? More specifically: will the `// NOLINT(runtime/explicit)` comment disable all clang-tidy checks or none? https://reviews.llvm.org/D40671 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
