Why do gcc-go and go are in conflict?

Question

Hi.
I just found that gcc-go and go are now in conflict. I just removed go when upgrading, but was curious about the reason.
I'm new to Go and I really don't know the benefits of one compiler over the other, so I had this whim of having both installed togheter.
Thanks.

Answer 1

Go user and active Go development list follower here. The thing is that gcc-go now has it's own version of the "go" command that should be a closely following fork of the one in the "go" package and is primarily there to make gcc-go work more easily on architectures where the standard go distribution is not available.
The "go" command in the standard distribution (the go package) has support for gcc-go too though so that gcc-go and go can work together. So I think the best solution would be to install the gcc-go binaries that conflict with "gcc-" prefixed or disable them during configure.
On x86 and x86_64 the go package is the more advanced Go implementation and should be preferred (gcc-go lacks escape analysis currently and has less advanced garbage collection especially once go 1.5 is released)