News for hackers. Stuff that matters.
Re:Simpler and faster GC for Go by k0t0n0 on Thursday July 17, 2014 @07:39AM (#8046933)
God of Speed Dmitry Vyukov.
Re:Simpler and faster GC for Go by andrewchambers on Thursday July 17, 2014 @07:48AM (#8046962)
Dmitry is in my personal programmer hall of fame.
Re:Simpler and faster GC for Go by eloff on Thursday July 17, 2014 @10:11AM (#8047587)
Ditto, the guy is a real software engineer.
Re:Simpler and faster GC for Go by shurcooL on Thursday July 17, 2014 @04:32PM (#8050038)
Yeah, it was an honor to meet and talk with him in person at the last golang meetup. His incredible work is inspiring and motivating.
Re:Simpler and faster GC for Go by kyrra on Thursday July 17, 2014 @10:04AM (#8047555)
I don't see this on golang-dev at all. I'm interested to see the discussion around it.
Re:Simpler and faster GC for Go by cjslep on Thursday July 17, 2014 @10:58AM (#8047879)
The code review has discussion: https://codereview.appspot.com/106260045
Re:Simpler and faster GC for Go by hyperliner on Thursday July 17, 2014 @06:53PM (#8050708)
I agree.

But it has always bothered me how he declares pointers! :-)

(stack[pointer] s, node[pointer] n)

Instead of

(stack [pointer]s, node [pointer]n)

Am I picky? :-)

[pointer] is the * just trying to avoid the italics conversion of HN.

Re:Simpler and faster GC for Go by shurcooL on Friday July 18, 2014 @01:06AM (#8051754)
I remember I was going back and forth between the two over the years, and I had to keep looking up which was my "latest" preferred style.

I eventually came to the following,

(stack [pointer] s, node [pointer] n)

Since it's symmetrical, it's easy to remember.

Luckily, I've been using Go and gofmt (goimports, specifically) the last 2 years so this is no longer an issue.

Re:Simpler and faster GC for Go by babawere on Saturday July 19, 2014 @04:01AM (#8056969)