cmd/vet: support cgo packages #4889
Closed
Comments
Related to this issue is the following example. b.go located at: http://play.golang.org/p/dyr3_PAwhl [~]$ go vet b.go b.go:10: arg for printf verb %s of wrong type: invalid type exit status 1 The error is no longer "could not import C (can't find import: C)", but instead an inaccurate vetting error. |
I think my issue probably just got fixed: https://code.google.com/p/go/source/detail?r=eb28a75cdc403bcb2ba0210893494ca8a71c6e1e |
A number of the examples in this issue work now because they were unrelated to the main topic. Recent changes have made go vet more robust and accurate even when typechecking fails. Top example: z.go:7: arg 5 for printf verb %s of wrong type: int Second example: silence. Deferring to 1.3; the cgo issue that is the real one here remains hard. Labels changed: added go1.3maybe, removed go1.2maybe. |
Close the issue for now as it has remained inactive for more than 6 months. Anyone with more insight into the current status may re-open the issue or add a comment about the current progress. |
I thought @mdempsky was still interested in this. |
Matthew, you may re-open this issue if you are still interested in it. I decided to close it, as it had been placed in the Go "black hole" that is the unreleased milestone. Didn't mean to close it if you still had an interest in it. Cheers /u |
Change https://golang.org/cl/74750 mentions this issue: |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The text was updated successfully, but these errors were encountered: