Go Gotchas

[Bjorn Roche]

I've been using Go irregularly for about a year and I like it a lot. I have yet to really dive in deep with it.

I've found a few "Gotchas" on my own, and wonder if you could share what you think are the biggest gotchas.

The biggest Gotchas I've found is this:

type T struct {   index int } ts := make([]T,0) // populate ts for i, t := range ts {    t.index = i //doesn't actually change anything in ts }

I understand why this is, but I nevertheless make the mistake.

[Matt Farina]

On Gotcha that I had to learn early on is that the application exits when main finishes. Even when there are concurrent goroutines doing work you intend. To avoid that there are ways to make sure main waits for the other work to finish before exiting.

Because of the way Go handles concurrency that can run on multiple threads this seemed like a fairly unique one to Go. We do cover waiting in Go in Practice.

This was one I had to learn the hard way.