[clang-tidy] method for NOLINT whole file

[nickdesaulniers]

https://clang.llvm.org/extra/clang-tidy/#suppressing-undesired-diagnostics mentions that:

The NOLINT comment instructs clang-tidy to ignore warnings on the same line (it doesn’t apply to a function, a block of code or any other language construct; it applies to the line of code it is on).

For implementing assert.h in llvm-libc, you literally do not want a header guard. To suppress llvm-header-guard, we need to add NOLINT(llvm-header-guard) as the very first line to this header, BEFORE the license comment, which is also against the style guide.

It would be nice if we had another method for silence this clang-tidy diagnostic somehow within this file.

[llvmbot]

@llvm/issue-subscribers-clang-tidy

Author: Nick Desaulniers (nickdesaulniers)

https://clang.llvm.org/extra/clang-tidy/#suppressing-undesired-diagnostics mentions that:

> The NOLINT comment instructs clang-tidy to ignore warnings on the same line (it doesn’t apply to a function, a block of code or any other language construct; it applies to the line of code it is on).

For implementing assert.h in llvm-libc, you literally do not want a header guard. To suppress llvm-header-guard, we need to add NOLINT(llvm-header-guard) as the very first line to this header, BEFORE the license comment, which is also against the style guide.

It would be nice if we had another method for silence this clang-tidy diagnostic somehow within this file.

[nickdesaulniers]

@cjdb point out that NOLINTBEGIN and NOLINTEND can be used for entire file nolints

https://clang.llvm.org/extra/clang-tidy/#suppressing-undesired-diagnostics