My guess is that part of this was my fault, not Go's. We had some issues with Go being installed in different locations on the CS department machines than on t

My guess is that part of this was my fault, not Go's. We had some issues with Go being installed in different locations on the CS department machines than on the campus-wide compute infrastructure machines. Within the projects, we also had a somewhat convoluted directory structure in which to mix official code (e.g., interface definitions) that the students weren't supposed to modify and stub code that they were supposed to change. I hope to simplify it a bit for next year. So I'd take this with a little grain of salt: I expect many fewer compilation problems next year just by having had go1 installed for a year and it becoming stable in our environment.