1
0
mirror of https://github.com/golang/go synced 2024-11-18 16:14:46 -07:00
go/cmd/vet/testdata
Rob Pike c333e7a7b6 go.tools/cmd/vet: fix go.tools build
TBR: gri

I cannot create an issue on the tracker for some reason, so here it is:
go vet contains this snippet:

        if types.IsAssignableTo(typ, errorType) || types.IsAssignableTo(typ, stringerType) {

It's getting the wrong answer: It claims

interface {
        f()
}

or even

interface {
        f() float64
}

matches the Error and Stringer interfaces. Both of them.  This causes a test failure:
$ go test code.google.com/p/go.tools/cmd/vet
BUG: errchk: testdata/print.go:124: missing expected error: '"for printf verb %s of wrong type"'
$
This worked until very recently.

R=gri
CC=golang-dev
https://golang.org/cl/12398043
2013-08-03 15:56:56 +10:00
..
asm1.s go.tools/cmd/vet: use "go test" to test 2013-05-22 10:20:50 -07:00
asm2.s go.tools/cmd/vet: use "go test" to test 2013-05-22 10:20:50 -07:00
asm3.s go.tools/cmd/vet: use "go test" to test 2013-05-22 10:20:50 -07:00
asm.go go.tools/cmd/vet: use "go test" to test 2013-05-22 10:20:50 -07:00
assign.go go.tools/cmd/vet: use "go test" to test 2013-05-22 10:20:50 -07:00
atomic.go go.tools/cmd/vet: use "go test" to test 2013-05-22 10:20:50 -07:00
buildtag_bad.go go.tools/cmd/vet: use "go test" to test 2013-05-22 10:20:50 -07:00
buildtag.go go.tools/cmd/vet: use "go test" to test 2013-05-22 10:20:50 -07:00
composite.go go.tools/cmd/vet: the composite test is about keys, not tags 2013-08-03 12:19:59 +10:00
deadcode.go go.tools/cmd/vet: use "go test" to test 2013-05-22 10:20:50 -07:00
method.go go.tools/cmd/vet: use "go test" to test 2013-05-22 10:20:50 -07:00
print.go go.tools/cmd/vet: fix go.tools build 2013-08-03 15:56:56 +10:00
rangeloop.go go.tools/cmd/vet: use "go test" to test 2013-05-22 10:20:50 -07:00
shadow.go go.tools/cmd/vet: add check for shadowed variables 2013-06-21 11:27:53 -07:00
structtag.go go.tools/cmd/vet: use "go test" to test 2013-05-22 10:20:50 -07:00