About the code formatting I wonder whether it's possible to leave some flexibility and not to have define every little detail. If you look at https://clang.llvm.org/docs/ClangFormat ... tions.html
you will see how many things can be handled differently and for many of them I personally don't care what's used (e.g. all the Align* options).
For me the most important point is readability. Nothing is more tedious and tiring to review unreadable code because of poor formatting. This does not only considerably reduce maintainability but also increases the likelihood to overlook serious bugs or later introduce them unintentionally.
At the moment a lot of FreeCAD code looks very squashed where adding some newlines would already help a lot to more easily understand what it is supposed to do. Therefore I suggest e.g. for lengthy (and nested) if-else cascades to put the else
keyword to the next line after a brace.
Or often there are if-else constructs where in one else-branch curly braces are used because the body consists of several lines but in the next branch they are omitted because it consists of a single line. In this case most coding styles recommend to use curly braces for all bodies if at least one body needs it.
Or if a branch of an if-else block has only one statement but an additional comment curly braces should be used, too.
Indeed. All I see is unnecessary complication. All was easy before. Now, suddenly, if i want to add an exception, I have to fight yet another complicated system. One invented just for making code look good, that happens to prevent my code from looking good.
We need at least some coding styles where the readability is harmed at the moment.