Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Specify a code style via clang-format --style=webkit #36

Merged
merged 1 commit into from
May 4, 2024

Conversation

motiejus
Copy link
Collaborator

@motiejus motiejus commented May 3, 2024

clang-format --style=webkit is closest to the current style. Most notably, calling_a_function ( "has more spaces now" ) than calling_a_function("would have in this change")

Let me know what you think. The files were changed with make lint.

@motiejus
Copy link
Collaborator Author

motiejus commented May 3, 2024

@mikesart I understand there is a high chance you may not like it and I obviously respect that. Feel free to play around with different styles (clang-format --style=<...>) and see if you like anything more. Webkit is my favorite, but again, I am not a C programmer by the day.

I noticed there hasn't been anything to automated formatter, so let's see if anything sticks.

@mikesart
Copy link
Owner

mikesart commented May 3, 2024

I wind up working in a bunch of codebases, so as long as things are consistent I'm happy. If you like this one then +1 from me on applying to all the current files and committing. Thanks Motiejus.

clang-format --style=webkit is closest to the current style. Most
notably, `calling_a_function ( "has more spaces now" )` than
`calling_a_function("would have in this change")`

Let me know what you think. The files were changed with `make lint`.
@motiejus motiejus merged commit 65c47f5 into mikesart:master May 4, 2024
5 checks passed
@motiejus motiejus deleted the clang-format branch May 4, 2024 10:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants