rob05c opened a new issue #2077: Write Go Coding Style Doc URL: https://github.com/apache/incubator-trafficcontrol/issues/2077 Most of the Go Coding Style is covered in https://golang.org/doc/effective_go.html and https://github.com/golang/go/wiki/CodeReviewComments but not everything. For example, two notable things: * don't use relative import paths. They are pain. * don't vendor `golang.org/x`, treat it as part of the compiler, because old `x` breaks with new compilers. Another example is, that the Go community has widely agreed that named return params are confusing and shouldn't be used, even though the Go authors like them.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
