Thanks for the quick response :) Great to hear that the go tool is intended to catch this. The problem was typically seen when running our default make target, which uses build for the build itself, but has some sanity checking and code generation steps first, with tools like glock, errcheck and mockgen. I think that most failures were in this first phase. Could it be possible that we hit this as a result of usage of the ast package or importgraph within these tools? If so, clearing the pkg directory may have been a red herring.
I can try to reproduce this later this evening and see if I can pin down the exact culprit. -- 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.
