Why not accept a universal format instead of wasting time sperging out about tabs vs spaces on the web? Treating stylistic freestyle as compile errors in go is a nontrivial comtribution to the success of the language.
Just adhere to the style of the code section. If you commit refactoring with other changes you are doing it wrong anyway. I want to see your changes and I don't want to scroll through a red sea of slightly changed variable names.
This is just another instance of modern software "development" aka bikeshedding Olympics.
Name:
Anonymous2019-05-29 9:09
True.
Auto formatting as in emacs or 4coder is the way to go. Saves a lot of brain power and typing.