Learning Go by porting a medium-sized web back end from Python

Re:Learning Go by porting a medium-sized web back end from P... by yla92 on Thursday November 09, 2017 @10:28AM (#15663174)

> gofmt is a good idea (just like clang-format or yapf), and having it is great, but the maintainers specifically refuse to add simple features, saying "running it in an automated process is not supported", despite all github projects already having it in their automated CI suite

A Golang noob here. Can you (or anyone else) expand more on this? Are there any links that I can read more about this?

[ Parent | on HN ]

Re:Learning Go by porting a medium-sized web back end from P... by 4c2383f5c88e911 on Thursday November 09, 2017 @10:35AM (#15663227)

Actually, the mistake is mine, I meant to write golint (but too late to edit). I have no issue with gofmt. As for golint, https://github.com/golang/lint/pull/100 is the kind of thing I'm thinking about.

[ Parent | on HN ]

Re:Learning Go by porting a medium-sized web back end from P... by weberc2 on Thursday November 09, 2017 @12:47PM (#15664307)

The Go team aren't the most respectful, but I think Dsymonds is uncharacteristically rude. Most of my experiences with the rest of the Go team have ranged from "sorta terse, but I'll give the benefit of the doubt" to very positive.

[ Parent | on HN ]