-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Run golint and deadcode and consider cleaning #91
Comments
Yep -- we are planning to do a gometalinter over the whole codebase in the near future and chase down all the issues. |
Now there are only documentation warnings:
Once they will be resolved we can CI on |
Actually, I ran only on the top level |
Lint should be done by |
I'd suggest a stronger approach to linting that what you have there. The golangci-lint metalinter does a good job and allows exclusions. The SAAS that they used to provide doesn't exist anymore, but it can be replicated in your CI. We do it like so: https://github.com/gonum/gonum/blob/master/.travis/script.d/check-lint.sh |
This looks really cool. If you'd like to integrate this approach it would be very welcome. |
golint . | wc -l
prints 534. 191 of these are not due to lack of documentation and can be cleaned relatively easily. The rest probably deserves a "needs documentation" issue.find -type d -exec deadcode '{}' \;
identifies two non-codegen instances of unused code. These are also easily cleanable (one -cpuprofile
is the subject of a PR, the other isgraph/iterator/fixed_iterator.go:53:1: newFixed
).The text was updated successfully, but these errors were encountered: