2 ms·
I looked at the code and it did not feel good. Go's ecosystem focuses on line-of-sight coding, that is, happy path has the least indentation, unhappy path (e.g.
by Cthulhu_ 6y ago
I looked at the code and it did not feel good. Go's ecosystem focuses on line-of-sight coding, that is, happy path has the least indentation, unhappy path (e.g. test failures in the naive / default unit test approach) should be indented. This tool seems to do a lot of indentation.
I know it's a bit of an arbitrary thing, but it's a good rule of thumb. And it's consistent with the other 99% of Go code, which is really important.