Slightly better reporting

[lordofscripts]

I ran into this wonderful tool because my GitHub workflow was failing because the GitHub server is using a different GO version in that build environment. I had a misunderstanding of the go.mod as well.

I would be nice that when you run without -v verbose mode with either -check or -strict that it at least tells the user "OK" rather than finishing silently.

[lordofscripts]

I cloned it locally to make it the output easier to read and more appealing to me at least:

mingo-los -v -check
    1 cipher_enum.go:69:3            (function body with no final return statement)
    9 version.go:72:6                (type alias)
   10 mcaller_info.go:61:9           ("strings".Builder)
   13 mlog.go:64:27                  (expanded numeric literal)
   14 mlog.go:83:66                  ("log".Lmsgprefix)
   16 mlog.go:149:19                 ("os".OpenFile)
   18 util.go:298:1                  (generic func decl)
   22 affine_helper.go:84:2          (range over integer)

[bobg]

Thanks for this suggestion!

I don't want to change the behavior of -check. In keeping with other checking tools (like go vet or staticcheck), the absence of output is idiomatic to mean things are OK. I'm not averse to adding a -ok or -status flag or something, however, to do what you want. Would you like to open a pull request?

As for your updated -v output format: again, starting each line with filename:linenum: is idiomatic for these sorts of tools, and helps them to interoperate with other tools in the ecosystem; but a -pretty flag might not be a bad idea.