Enforce consistent code style
Mc wrote:
_clang-format was (loosely) created from that textual description, which was (loosely) created from existing and desirable style
what would be logical would probably be : we put in the _clang-format what we consider desirable; then we update the textual description to fit it, then we stick to it for new/reformated code
TODO list:
- define reference source files with near-to-perfect style
- define "negative reference source" to be badly auto-formatted files with current
_clang-format
- update
_clang-format
to minimize reformat changes to "reference sources" and "negative reference source" - update textual description to match
_clang-format
at https://inkscape.org/develop/coding-style/ - establish procedure of migrating existing sources to new style. (Possible options: reformat all at once | reformat whole file on PR | reformat part of file on PR |
<your option here>
) . - [optional] enforce code style check in CI in PR
Please post "reference style sources" as well as "negative reference source" to make code style tweaks more precise.
Edited by Jonathan Neuhauser