> but it seems like in practice this doesn't come up too often in Go? It comes up in any language that allows shared mutable state, so not much in functional l

> but it seems like in practice this doesn't come up too often in Go? It comes up in any language that allows shared mutable state, so not much in functional languages which discourage mutability or Rust which discourages shared mutability. On the other hand, most code tries to avoid shared mutable state by convention, there’s a nice bit in the Go lang design article that basically says convention is good enough, significantly simplifies the language, at the cost of the odd bug.