Golang Data Structures

This is your reference when you need to think about Go data structure internals rather than just reaching for the first thing that works. It covers slice capacity growth mechanics, map bucket implementation, when to actually use container/heap or container/ring, and the strings.Builder versus bytes.Buffer question. The real value is in the preallocation guidance and the unsafe.Pointer patterns, which follow the six valid conversions from the spec. If you're writing generic collections or trying to decide whether a weak pointer makes sense for your cache, the examples are concrete. Pairs well with the golang-safety skill from the same author for the aliasing and nil map traps.