Comment 1:

Can you be more specific? There is one that should be fixed (Printf(os.Stderr) gives
only a warning) but the only other Warnf call in print.go is a type-checking failure
that is unlikely unless go/types failed on the package. In that case the diagnosis is
really only a warning.
There are a few Warnf calls in other modules that should be made Badf but you explicitly
called out print checking.

Comment 2:

I called out print checking, not because it's necessarily wrong, but because I noticed
it was different to some others. Is it your intention that govet should exit with 1 if
there are problems it finds? That sounds okay to me, but (1) it should be documented,
and (2) the few warnings that don't use Badf should be fixed. It just wasn't clear to me
what the exit value semantics were supposed to be.

Comment 3:

This issue was closed by revision 8cf6e75.

Status changed to Fixed.