| Examples that bother me sometimes. YMMV of course. Writing to a closed channel panics, but writing to a nil channel blocks forever. Appending to a nil slice works fine, but inserting into a nil map panics. If you have a function that returns an error struct, and you wrap it with another function that returns the error interface, nil returns from the inner function will no longer test equal to nil. Defining a method with a receiver type of Foo, rather than <star>Foo, means all modifications to the Foo get silently dropped. This can also happen to methods that correctly take a pointer receiver, if their caller incorrectly takes a value receiver. Maps are not threadsafe/goroutine-safe. Expression evaluation order is not defined, and varies between compilers. (https://github.com/golang/go/issues/15905) |