This what you wanted? To be a janitor? Live like this? All this? Do what you do? It can’t be. It’s a burden, that’s what I’m trying to tell you. That’s how it feels.
Michael Clayton (2007)
The exports module prints exported identifiers in Go source code.
Starting with StaticCheck 2020.2, whole-program mode was removed. it now operates like this:
The normal mode of 'unused' now considers all exported package-level identifiers as used
So we need to unexport all symbols using some tactic. This will then give us agency. StaticCheck will then report symbols as unused, which we can respond to by either exporting them or removing them.
If you use a command line this:
gofmt -w -r 'NewBuffer -> _NewBuffer' .
It will also catch imported functions like
bytes.NewBuffer. You could try to
fix like this:
gofmt -w -r 'a._NewBuffer -> a.NewBuffer' .
but it will also catch method calls:
we could try hardcoding the exceptions:
gofmt -w -r 'bytes._NewBuffer -> bytes.NewBuffer' .
but the imported method calls will still be broken:
we can use this:
rf 'mv FinishedHash _FinishedHash'
but it only works for a single identifier. Can we print out all identifiers?
May 10, 2020:
We found that 154.pages.dev/exports demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket installs a GitHub app to automatically flag issues on every pull request and report the health of your dependencies. Find out what is inside your node modules and prevent malicious activity before you update the dependencies.