aboutsummaryrefslogtreecommitdiffstats
path: root/src/.clang-tidy
AgeCommit message (Collapse)AuthorFilesLines
2022-04-23Move reserved platform defines from code to build systemDavid Robillard1-4/+0
Numerous things warn about this, and it's generally a bad idea to put these in the code since it can result in incompatibly compiled code being linked together. Unfortunately this makes building manually (without the build system) more fiddly, but such is life.
2022-04-23Suppress warnings when building with clang on WindowsDavid Robillard1-0/+1
2021-12-17Suppress new warnings in clang-tidy 13David Robillard1-1/+2
2021-08-28Suppress new clang-tidy warningsDavid Robillard1-0/+2
2021-05-06Strengthen clang-tidy warningsDavid Robillard1-2/+0
2021-05-06Clean up X11 implementationDavid Robillard1-1/+0
2021-01-02Avoid "else" after "return"David Robillard1-2/+0
2020-11-22Suppress various clang-tidy warningsDavid Robillard1-0/+5
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-11-01Run clang-tidy on all headers and fix various issuesDavid Robillard1-0/+2
It's a nightmare trying to get this thing to check everything.
2020-10-30Move implementation source files to a conventional src directoryDavid Robillard1-0/+12
I think this attempt to be optionally header-only was misguided, particularly installing source code to the system include path. Typically anyone vendoring code just includes the repository and builds from there anyway. This commit moves all the implementation code to a typical src directory (Don't Be Weird). I still think there is some value in simple "inline" deployment, but that would be better achieved another way, like producing a single-file amalgamation that builds anywhere, ala sqlite.