4 ms·
I have already used one such tool for C++ in one of my teams (aastyle ? Something like that). It's only the firs step. Then you have to wonder/discuss: what act
by sacado2 11y ago
I have already used one such tool for C++ in one of my teams (aastyle ? Something like that). It's only the firs step. Then you have to wonder/discuss: what actual style to use? There are many C/C++ styles out there (stroustrup, linux, gnu, OTBS, etc.), so you have to discuss about that. Now, when you have chosen one, you have to discuss about minor fixes: "ok, so OTBS is cool, but what about line lengths? Should we choose 80 cols? That's silly, why not 120?"
etc. All in all, you end up taking a whole hour (even more) about this issue.
With go, that doesn't happen. You call gofmt and you're done. Another side effect: when you get external source code (open source, code written by another team, etc.), you know it will be formatted exactly the same way as yours.
- spion 11y agoI'm afraid that may be your fault. What style you pick doesn't matter much (consistency does though) so you should just pick one. It really baffles me that anyone could spend so much time on something like that. I'm sure there are lots of more exciting (or more pressing) problems to solve on the projects you're working on...