Every story and comment from the Hacker News API, in a layout borrowed from 2001.
A comment on Go: Redefining For Loop Variable Semantics. Parent comment
That's what go does under the hood in 95% of cases. If I do:
func foo(a int) int { return &a }
func main() { fmt.Println(foo(3)) }
It does the right thing. It's just that in this case (and in lambdas) they got it wrong.
There are no comments on this comment yet.
That's what go does under the hood in 95% of cases. If I do:
func foo(a int) int { return &a }
func main() { fmt.Println(foo(3)) }
It does the right thing. It's just that in this case (and in lambdas) they got it wrong.