aboutsummaryrefslogtreecommitdiffstats
path: root/examples/.clang-tidy
AgeCommit message (Collapse)AuthorFilesLines
2024-10-01Suppress new warnings in clang and clang-tidy 18David Robillard1-1/+4
2023-11-11Suppress new warnings in clang-tidy 16David Robillard1-1/+5
2023-10-21Suppress clang-tidy C++ warningsDavid Robillard1-0/+1
2023-01-04Clean up licensing metadataDavid Robillard1-0/+3
2022-10-07Avoid C-style casts in C++ codeDavid Robillard1-1/+0
2022-10-07Simplify clang-tidy configurationDavid Robillard1-8/+1
2022-10-07Suppress new warnings in clang-tidy 14David Robillard1-0/+3
2022-06-28Simplify clang-tidy configurationDavid Robillard1-5/+1
2021-12-17Suppress new warnings in clang-tidy 13David Robillard1-1/+2
2021-08-28Suppress new clang-tidy warningsDavid Robillard1-0/+4
2021-05-28Remove static downcasts in C++ bindingsDavid Robillard1-2/+1
2021-01-02Avoid "else" after "return"David Robillard1-2/+0
2021-01-02Fix clang-tidy warningsDavid Robillard1-1/+5
2020-11-22Suppress various clang-tidy warningsDavid Robillard1-0/+7
These libc-specific warnings are a new level, even for LLVM. Using an opt-out style for this is probably not going to last.
2020-10-28Add Vulkan demosDavid Robillard1-0/+11
2020-10-21Use separate clang-tidy configurations in different directoriesDavid Robillard1-0/+20
This allows more fine-grained control. In particular, it prevents mistaked from creeping in to the public headers or core implementation because of warnings that are disabled for the tests and examples. This keeps the code that is used in other projects as clean as possible.