Closed vhotspur closed 10 months ago
Can I play with .clang-format
settings too? :-)
Can I play with
.clang-format
settings too? :-)
Are you in such hurry? I still have some stashed changes and I am adding the rules slowly so that I can still reasonably review that the automated formatting have not broken anything.
And no, there will be no spaces in function calls ;-).
Can I play with
.clang-format
settings too? :-)Are you in such hurry? I still have some stashed changes and I am adding the rules slowly so that I can still reasonably review that the automated formatting have not broken anything.
Not really in hurry. I'm just asking for general permission to potentially chime in, because I don't like how clang formats some of the things :-)
And no, there will be no spaces in function calls ;-).
I would not dare... :-)
I’m curious about how this change will handle some of the uglier parts of the code I’ve written (mostly the parts with C macros). Perhaps it would be better to refactor these part so they are written more reasonably.
I’m curious about how this change will handle some of the uglier parts of the code I’ve written (mostly the parts with C macros). Perhaps it would be better to refactor these part so they are written more reasonably.
That's the plan after we clean up/unify/enforce formatting, so that refactoring is not mixed up with formatting changes.
I'm just asking for general permission to potentially chime in because I don't like how clang formats some of the things :-)
Now is the right time :-).
I think I have covered the most offensive parts (at least for me) and now the C style is enforced so things will only improve™.
Summary of changes
#include
s sortedI would like to merge this before any further (functional) changes are made to prevent conflicts.
Convert to a unified C style (enforcing new rules in each commit) with CI-enforced checks.
Changes applied and enforced:
#include
s sorted