OK. Since I haven't heard any opinions from anyone else here yet, I'm
inclined to stay "conservative" for now and leave the code formatting as
it is.
On 08/09/2015 05:01 PM, Benjamin Barenblat wrote:
On Sunday, 9 August 2015, at 11.28 am EDT, Adam Chlipala wrote:
It's not obvious to me […] that it's worth the complexity of integrating
a tool like this into the development workflow […].
Is the current official code so hard on the eyes? :)
No, but potential contributors do look at nitpicky things like style
consistency when judging the quality of a project and deciding whether
or not to participate. If style is consistent and enforced through a
tool like clang-format, more people are likely to contribute.
As for integrating clang-format into the development workflow, it’s as
simple as running that clang-format command from the previous e-mail
before committing. One could even add it as a pre-commit hook and
forget all about it.
_______________________________________________
Ur mailing list
[email protected]
http://www.impredicative.com/cgi-bin/mailman/listinfo/ur
