Hacker News Reader

> Loop variables being per-loop instead of per-iteration is the only design decision I know of in Go that makes programs incorrect more often than it makes them correct. Since it is the only such design decision, I do not see any plausible candidates for additional exceptions.

The bar is quite low.

View on HN

It's also very subjective. Just off the top of my head I can think of:

- zero values instead of sum types

- nil, especially on interfaces

- goroutines sharing memory

- goroutine panics not being raised in the spawner by default

golang has quite the suspect decisions that show up when writing large programs https://www.uber.com/blog/data-race-patterns-in-go/

Working link: https://www.uber.com/en-US/blog/data-race-patterns-in-go/

(For me, the link you posted does a 302 redirect to https://www.uber.com/pt-BR/blog/data-race-patterns-in-go/ which gives me a 404 error page. It's a bit insane that whether the link you posted works or not depends on your locale, and unfortunately this is not the first time I've seen this kind of baffling redirect misbehavior.)

Reply on news.ycombinator.com