> Furthermore, mixing C code with Go code can cause performance issues if not done right. While you can expect the official project to "do it right", this still

> Furthermore, mixing C code with Go code can cause performance issues if not done right. While you can expect the official project to "do it right", this still raises the bar for people who know Go and want to contribute, but don't know C as well. This is why Go was maintaining it's own C compiler -- They had it modified to work well with Go, as far as I am aware[1]. Removing it means one less compiler to maintain. [1] From Go 1.4, the source for the Go C compiler: https://github.com/golang/go/tree/883bc6ed0ea815293fe6309d66f967ea60630e87/src/cmd/6c https://github.com/golang/go/tree/883bc6ed0ea815293fe6309d66...