codecoroner
codecoroner copied to clipboard
3rf
tool for detecting unused functions and variables in Go source code
It'd be great if we can use that tool to then delete those unused functions
For style consistency a method receiver variable might be defined for all methods of a type even for methods where the receiver is not used. Signaling unused method receivers variables...
``` type set f(str string) ``` `str` should not be reported as unused as `str` is useful as documentation. Note: this is a particular subcase of #21.
Unused variables defined in the signature of a function should not be flagged as unused because those variables names are helpful as documentation even if not referenced in the function...
See build [#45.1](https://travis-ci.org/3rf/codecoroner/jobs/228923225) for Go 1.5
When using codecoroner it would be useful to use exit code to detect any errors instead of parsing stdout/stderr. Suggesting to add a non zero exit code if codecoroner found...
Many static analysis tools have ways to explicitly say "don't bother with this" in the code. Is there any way in my code to say "ignore this function please, codecoroner"?...
The README doesn't give me any information on why I might choose this tool versus github.com/remyoudompheng/go-misc/deadcode from https://github.com/remyoudompheng/go-misc.
Since this pkg relies heavily on Google packages with little external usage, it would be nice to vendor things to prevent disasters like the removal of callgraph analysis from the...
