-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dynamic_modules: exclude abi.h from clang-tidy #37317
Conversation
Signed-off-by: Takeshi Yoneda <t.y.mathetake@gmail.com>
cc @phlax |
Note: I wanted to use |
so as discussed in #37320 clang-tidy is currently disabled in the CI, so the change here is not checked there... At least it's working locally ;) |
Signed-off-by: Takeshi Yoneda <t.y.mathetake@gmail.com>
@phlax i went ahead and simply put the header in the ignore target of clang-tidy - see the description of the PR for detail! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, thanks @mathetake
…#37378) This directive was introduced in #37317 but turns out this is not available in LLVM 14. So for now we remove this. By the time we enable clang-tidy on CI we should find a way to ignore it, but for now simply remove it so that we can run clang-tidy locally. part of #28566 Signed-off-by: Takeshi Yoneda <t.y.mathetake@gmail.com>
Commit Message: dynamic_modules: dynamic_modules: exclude abi.h from clang-tidy
Additional Description:
This commit disables clang-tidy for the whole ABI header which is a pure C file.
Previously, I added
// NOLINT
comment line on each place,clang-tidy is only for C++ source code, so this disables it considering the
readability. This shouldn't be a problem as the header only has types and
function declarations.
Risk Level: none
Testing: n/a
Docs Changes: n/a
Release Notes: n/a
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]