mistake -- on the contrary, I think it was inevitable. At the time, we were deeply mired in the C mindset, slightly above assembly language and convinced that any language construct that generated significant thinking in Go. If you take a higher point of view and start analyzing the problem from within the Go mindset, often a different approach suggests itself which leads to an elegant and idiomatic Go-solution