Closed karalabe closed 5 years ago
@karalabe Can I take this too ?
Sure!
should be closed now i guess @karalabe @ferhatelmas
Can I work on this?
@RichardH92 there were some deficiencies with linter itself. However, for sure, see for yourself since there might be something I had missed at that time.
@karalabe Starting to look into if I can help at all! 🤓 🤓
I started working on this, so far I enabled the linting on my fork. I will start fixing the linting errs, but this may take some time.
Create WIP pull req https://github.com/ethereum/go-ethereum/pull/16446
this can now be closed.
Can this issue be closed?
@karalabe can this issue be closed?
https://github.com/ethereum/go-ethereum/pull/16446 got merged, closing this issue
Continuing our CI linter efforts, it would be nice to have Go's
deadcode
linter enabled on our CI infrastructure to detect and report leftover code from refactors. Enabling the linter is simple enough:Beside enabling the
deadcode
linter, this task would entail looking though the generated warnings and fixing them. Note, some code is "dead", but shouldn't necessarily be deleted (e.g. the currently unused Ledger protocol constants)... for these, a nicer solution is needed sodeadcode
remains silent, but the constants remain in the code nonetheless.Currently reported issues are: