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 ...
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: