- May 11, 2021
-
-
Brad King authored
-
- Jan 27, 2021
-
-
Ben Boeckel authored
-
Ben Boeckel authored
-
Ben Boeckel authored
-
Ben Boeckel authored
-
Ben Boeckel authored
-
Ben Boeckel authored
-
Ben Boeckel authored
-
Ben Boeckel authored
-
Ben Boeckel authored
-
Ben Boeckel authored
-
Ben Boeckel authored
-
- Nov 12, 2020
-
-
Ben Boeckel authored
These warnings can be fixed in the future, but are ignored for now.
-
Ben Boeckel authored
CMake has intentional recursion in its codebase, so avoid warning about occurrences.
-
- Apr 13, 2020
-
-
Ben Boeckel authored
CMake has lots of instances of this which is outside the scope of this topic right now.
-
Ben Boeckel authored
CMake isn't ready for this yet.
-
- Sep 16, 2019
-
-
- Sep 10, 2019
-
-
wahikihiki authored
Set the MinTypeNameLength option to an impossibly high value in order to limit the diagnostics to iterators. Leave new expressions and cast expressions for later.
-
- Sep 06, 2019
-
-
wahikihiki authored
-
wahikihiki authored
Now that clang-tidy-8 is used, we can remove the checks that have been renamed. Also enable a return-braced-init-list, because we don't have any violations for that one.
-
- Sep 04, 2019
-
-
wahikihiki authored
Annotate the remaining typedefs with NOLINT. Unfortunately, clang-tidy is not smart enough and suggests the use of using inside extern "C" blocks.
-
- Aug 20, 2019
-
-
wahikihiki authored
-
- Aug 05, 2019
-
-
Sebastian Holtermann authored
Enables the clang-tidy test performance-inefficient-string-concatenation and replaces all inefficient string concatenations with `cmStrCat`. Closes: #19555
-
- Jul 30, 2019
-
-
wahikihiki authored
Check the codebase with clang-tidy version 8, fix the low hanging fruits, blacklist the rest.
-
- Apr 02, 2019
-
-
Jakub Kalinski authored
-
Artur Ryt authored
-
- Jan 30, 2019
-
-
wahikihiki authored
clang-tidy 7 has an option to suppress this warning in macros which defaults to '1'. Set the option to '0' and silence the warning explicitly.
-
- Jan 29, 2019
-
-
- Jan 25, 2019
-
-
Suppress some cases in `Source/cmGeneratorExpressionNode.cxx` and `Source/cmUVHandlePtr.h` where a few older compilers require a user-defined default constructor (with `{}`).
-
- Jan 22, 2019
-
-
- Jan 17, 2019
-
-
- Jan 15, 2019
-
-
- Dec 15, 2018
-
-
wahikihiki authored
-
wahikihiki authored
-
- Nov 21, 2018
-
-
wahikihiki authored
Enable the check in .clang-tidy and fix all warnings.
-
-
- Nov 20, 2018
-
-
Fix some warnings that are new since clang-tidy version 4, and update `.clang-tidy` to suppress the rest.
-
- Sep 26, 2018
-
- Sep 24, 2018
-
-
Brad King authored
Our installation is producing false positives on move constructors and assignment operators that are clearly marked `noexcept`.
-
- Sep 28, 2017
-
-
Brad King authored
We still support compiling CMake on VS 2013 that does not support `noexcept`, so disable the clang-tidy diagnostic for now.
-