Remove clang-tidy warnings for static fields created by doctest #159
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
When writing unit tests with doctest, clang-tidy raises a warning at each invocation of the
TEST_CASE()
orSCENARIO()
macro, explicitlyfuchsia-statically-constructed-objects
andcert-err58-cpp
for my current version of clang-tidy. The root cause is the intended creation of static variables by the framework. As these warnings are not a consequence of the user written code and there are plenty of them for a big test suite, they should be disabled.This pull request adds an explicit suppression for these two tests at the responsible line in the implementation.
GitHub Issues
The warning
cert-err58-cpp
was already discussed in issue #115. The solution provided there however requires some action by the user.