News for hackers. Stuff that matters.
Re:Go 1.5 is released by berfarah on Wednesday August 19, 2015 @06:26PM (#10088978)
This might be a dumb question: What happens if you find a bug in the language? Let's say something that you had written in C was being misinterpreted, and now the go compiler still uses that byte-code to compile new versions of the compiler.

Or is that something that isn't really possible?

Re:Go 1.5 is released by emmab on Wednesday August 19, 2015 @07:10PM (#10089149)
You should read Reflections on Trusting Trust, it expands on this idea in the most beautiful way: https://www.ece.cmu.edu/~ganger/712.fall02/papers/p761-thomp...
Re:Go 1.5 is released by jlouis on Wednesday August 19, 2015 @06:43PM (#10089053)
I think Russ showed the translated code produces the same binaries as the Go 1.4 C variant. So this isn't very likely given he has the option to pipe roughly any Open Source Go project through the compiler.