Initial pass at clang-format config #2352
Merged
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.
This is my best attempt at creating a clang-format config file that matches Cinder's current formatting. Probably the most egregious difference is that clang-format doesn't provide a mechanism for aligning
breakstatements withcaselabels llvm/llvm-project#58669.For Visual Studio users, this file is automatically detected and can be used without any additional configuration when working with the Cinder source code.
I think clang-format is useful enough and has become the accepted standard enough that it's worth modifying Cinder's code style to conform to a clang-format ruleset. However I personally wouldn't want to apply this to the codebase wholesale at this moment because just about every file would be touched to some extent (complicating git blames, among other things), but I'd propose any new code submissions make use of it.