|
@filipcodes | |||||
|
My experience with #golang taught me this: if your #programming language has a popular code formatting tool - use it, and use it *with the default settings*. The benefits of a single code formatting standard trump any subjective aesthetic preference in that regard.
|
||||||
|
||||||
|
James Mallison
@J7mbo
|
3. velj |
|
This is fine if it’s automated by a tool provided with the language. Problem comes when the language has 2. Anything else is entirely subjective, which “idiomatic go” is, and can be largely ignored. Enforcing subjectivity across a whole language is bordering purism and dogmatism.
|
||
|
|
||
|
Filip Wojciechowski
@filipcodes
|
3. velj |
|
Agreed. Also, if a given programming language has very powerful meta-programming abilities (like Haskell) this advice is difficult to implement since what qualifies as valid syntax can be fluid. Still, a good general rule, in my opinion.
|
||
|
|
||