-
Notifications
You must be signed in to change notification settings - Fork 492
Reopen issue #89 #491
Comments
I strongly suggest you ask for a refund! |
Please don't spam mentions in the future. |
Thanks, but, quoting the original response:
The lint program implements a certain set of style guidelines, that are now documented at https://golang.org/wiki/CodeReviewComments. If you want to follow a different set of style guidelines, modify or rewrite golint. The golint program is not intended to be all things to all people. |
I too can send a link to 31 people but that isn't a representative sample of users' opinions, nor is it a meritable argument on its own to take any action. Ignoring something and acknowledging it but not doing anything are different things. They should not be equivocated. |
God please don't make golint like eslint. Keep the rules consistent. Down with configurability. |
golangci-lint allows you to exclude certain messages, and supports golint. The license is GPL 2 which is fine for your personal use. I suggest you consider switching your tool chain to use that instead. As @ianlancetaylor said, it is not possible to make tools that are all things to all people, and those that attempt it invariably end up too complex. I don’t want to put words in anyone’s mouth, but reducing complexity in the tooling has generally worked well for the Go project and I wouldn’t expect that to change. I think you will be happier in the long run if you try to respect that the this issue is closed, and move on to golangci-lint which is a solution that is available to you immediately. |
|
Reopen issue #89
You shouldn't ignore your users' feedback.
The text was updated successfully, but these errors were encountered: