We've recently migrated from Go 1.6 to 1.7 within our engineering team, and have been experiencing some binary compatibility issues (as is to be expected) that have usually been corrected by emptying $GOPATH/pkg and rebuilding - this was recommended but as is the case with manual steps, people often skipped it.
Are there any other pitfalls that people have encountered migrating between point releases of Go? Better still, does anyone know of any tools we could include in our builds to sanity check the contents of $GOPATH/pkg? -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
