How Go improves expressiveness without sacrificing performance

Re:How Go improves expressiveness without sacrificing perfor... by bluesnowmonkey on Saturday February 11, 2012 @06:40PM (#3580515)

Can the optimizer not eliminate the redundant bounds checks in the "good idiomatic" version?

[ Parent | on HN ]

Re:How Go improves expressiveness without sacrificing perfor... by alec on Saturday February 11, 2012 @06:56PM (#3580550)

Check the first comment in the article - I can't believe that is actually good and idiomatic. The author uses the indexes, but the range command also supports returning the values.

To be fair, I have a lot of difficulty figuring out what's a reference and what's a value in Go; I suspect if it were an int and not a struct, that wouldn't work.

[ Parent | on HN ]

Re:How Go improves expressiveness without sacrificing perfor... by dhconnelly on Saturday February 11, 2012 @07:09PM (#3580585)

Only slices, maps, and channels are reference types.

[ Parent | on HN ]