Skip to content
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

.clang-tidy file is too open / not portable #108

Open
maldag opened this issue Apr 22, 2024 · 0 comments
Open

.clang-tidy file is too open / not portable #108

maldag opened this issue Apr 22, 2024 · 0 comments

Comments

@maldag
Copy link

maldag commented Apr 22, 2024

The used .clang-tidy activates all checks and disables just some of it. Upon integrating nanobench in another project which also uses .clang-tidy, probably in a different version, creates problems. The other version may introduce new checks which are implicitly enabled and not taken care of.

My suggestion would be to either disable .clang-tidy for integrations in other projects or explicitly activate just the checks that are to be checked. Testet with clang-tidy 17

The following checks cause new problems:

-llvmlibc-inline-function-decl
-modernize-use-nodiscard,
-modernize-type-traits,
-readability-named-parameter
#and there are more ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant