cmd/vet: failed import causes spurious printf error #17006
Closed
Comments
cc @valyala |
Prepared the CL. |
CL https://golang.org/cl/29014 mentions this issue. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The
printf
check issues a spurious error when type information for an imported printf-like function is not available. Without the function's type signature, the checker heuristically assumes that the first string constant is the format string, such as"a"
in the example above.The text was updated successfully, but these errors were encountered: