> the Go compiler is single pass, which considerably cripples the language and imposes a lot of weird asymmetric features. What evidence do you have that it c

> the Go compiler is single pass, which considerably cripples the language and imposes a lot of weird asymmetric features. What evidence do you have that it cripples the language? And can you point to a single 'asymmetric feature' (whatever that means) caused by this? If you read any of the interviews with Rob, he clearly points out that the compile speed has little to do with it being 'single pass', and all to do with the package system. In my subjective experience the compiler is way faster than Java or C# compilers, and they still have plenty of room to optimize compiler speed (for example, there is plenty of stuff the compiler could do in parallel but at the moment doesn't because they have tried to keep the toolchain as simple as possible specially while the language is changing so fast.)