Compare and contrast with deadcode

[sethwklein]

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.

[3rf]

Interesting point! I think one of the major differences is that go-unused-funcs/codecoroner is geared toward large multi-package projects by wrapping Google's static analysis packages, so that it can find unused exported code. The tool you linked to seems to only check on a per-package basis. For instance, one of the use-cases for my company involves a distributed system with multiple main packages, and our tool is able to check and see, accounting for each main pkg, what functions are dead in our common libraries.

Additionally I've been working on adding support for unused consts, variables, and fields, which will be detailed in the README shortly. I'll be sure to make these points while I'm redoing the README file--thanks!