Doing some code refactoring, and noticed that the vet half of the compile errors were sometimes printing out of source order
brendan:~/Documents/mygo/src/gonum.org/v1/gonum/optimize$ go test -v
# gonum.org/v1/gonum/optimize [gonum.org/v1/gonum/optimize.test]
./unconstrained_test.go:1185:18: undefined: Global
./unconstrained_test.go:1249:20: undefined: Global
./unconstrained_test.go:1302:10: undefined: Global
./unconstrained_test.go:1319:17: undefined: Global
# gonum.org/v1/gonum/optimize
./unconstrained_test.go:1319:17: undeclared name: Global
./unconstrained_test.go:1302:10: undeclared name: Global
./unconstrained_test.go:1185:18: undeclared name: Global
./unconstrained_test.go:1249:20: undeclared name: Global
vet: typecheck failures
I've made a .zip file of the code at the state right now that can be shared. It comes from a package with a lot of code, so it's hard to produce a minimal reproducer.
What did you expect to see?
I would have expected the errors to come in the same order as the compile errors.
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (
go version
)?1.11beta1
go version devel +a12c1f26e4 Tue Jun 26 20:00:51 2018 +0000 darwin/amd64
What operating system and processor architecture are you using (
go env
)?What did you do?
Doing some code refactoring, and noticed that the vet half of the compile errors were sometimes printing out of source order
I've made a .zip file of the code at the state right now that can be shared. It comes from a package with a lot of code, so it's hard to produce a minimal reproducer.
What did you expect to see?
I would have expected the errors to come in the same order as the compile errors.