Introduce clang-format and clang-tidy#16
Open
marcluque wants to merge 4 commits into
Open
Conversation
s3mme
force-pushed
the
main
branch
7 times, most recently
from
b80603f to
a67a03f
Compare
mormod
reviewed
Oct 15, 2022
Contributor
mormod
left a comment
mormod
left a comment
There was a problem hiding this comment.
Reviewing this, so the resulting .clang-format and .clang-tidy files can be used in Benzammour/yobemag
mormod
reviewed
Oct 15, 2022
mormod
approved these changes
Oct 15, 2022
Co-authored-by: Moritz Hüllmann <20692341+mormod@users.noreply.github.com>
marcluque
force-pushed
the
clang-format
branch
from
5053cbc to
f486a61
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 an initial proposal for a .clang-format and .clang-tidy setup. 739e3e5 and 25eea57 respectively show clang-format and clang-tidy changes.
I would suggest not looking at the changes, since github does not display everything correctly. Instead looking at the source directly should be better.
Some major points:
This addresses #13.