tree a92c01631f81d8af91f7c88dfba87f390087b449
parent 2809dbc3d6ef202ae00b52b8f2a982862a993f36
author Joe Tsai <joetsai@digital-static.net> 1513367142 -0800
committer GitHub <noreply@github.com> 1513367142 -0800
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJaNCZmCRBK7hj4Ov3rIwAAdHIIAAyR8YmXc6Zj+Gx4Gg8mYYSr
 HMPIa1CU9+m2b4OXfShe8MRyC2Nu9AgbBZ++cbOBnPFgRwl/GwouuF7GOoxloefQ
 8j2uvdn10BqgXrj+kXfO9NAWa63mHGrsFK3L7NEKfBF3sN5SjhwScK5rUhftXOKK
 u7YMbUnAqWkbqaKNDePT2l8XeztSpwpRt9/xlSFjJ/Zp0Te+UfnFNeP7R+6sOX6y
 oHIruoolSqGJxICUuiUi034xGkgG8hGfVdHfnIhUeMijYn62YdqrO3YztYgurrkR
 DbaUqzLO0GEAckp47LwBKKJEVWckQqau9o41MVhiG3ppWoryatlocH5NlzSlJSM=
 =YsY0
 -----END PGP SIGNATURE-----
 

Adjust Travis CI script (#60)

Rather than running gofmt for every version, leading to version skew
when what gofmt considers "correct" differs between versions,
only use one specific version of gofmt.

Also, remove the "-s" flag from gofmt because it is not backwards compatible.
Suppose Go1.11 allowed for elliding types on struct literals and the "-s"
flag strips them, then this would be problematic because it would not compile
on Go1.10 and earlier.

Also, fix the code so that vet is happy. I am not sure why these checks
were not triggered before. There seems to be a bug in the caching of
$GOPATH/pkg files. This may be fixed in Go1.10 by the new caching logic.
Running "go install" before running go vet fixes the issue.

In other words, the only check we perform for differing versions
is that the tests pass (and implicitly that it builds).