News for hackers. Stuff that matters.
Re:Porting the Go compiler from C to Go by beliu on Friday April 25, 2014 @12:59PM (#7647653)
Author of the post here. Happy to answer any questions I can, and FYI, we (Sourcegraph) are liveblogging all of GopherCon at http://gophercon.sourcegraph.com. Let us know if you have any questions or find it useful!
Re:Porting the Go compiler from C to Go by codezero on Friday April 25, 2014 @02:08PM (#7648117)
You might want to clarify that you aren't Russ Cox and that this post is a summary of a presentation he gave.
Re:Porting the Go compiler from C to Go by sqs on Friday April 25, 2014 @03:36PM (#7648603)
Thanks for mentioning this. I initially included "(unofficial liveblog post)" in the HN title, but it apparently was edited out by a moderator. So, I added a clarification to the top of the post itself.
Re:Porting the Go compiler from C to Go by nfoz on Friday April 25, 2014 @02:05PM (#7648092)
Are you at all concerned about the possibility of the Trusting Trust[1] problem manifesting in any of your Go compilers?

[1] http://cm.bell-labs.com/who/ken/trust.html

Re:Porting the Go compiler from C to Go by 0xdeadbeefbabe on Friday April 25, 2014 @04:41PM (#7648922)
Since this is an exercise divorced from reality, the usual vehicle was FORTRAN.

Dang it I cheated and looked up Rus's quine. For anyone not wanting to cheat a good hint would be "tail recursion"

Re:Porting the Go compiler from C to Go by zellyn on Saturday April 26, 2014 @12:43AM (#7650468)
It was suggested long ago that having multiple compilers would make it incredibly difficult to play Trusting Trust games.