Go Data Structures

Handles the practical decisions you run into when working with Go's core collections: when to use make versus a nil slice, why append needs assignment, how to implement sets with maps, and the aliasing traps with copying structs that have pointer receivers. The decision tree at the top is genuinely useful for picking between arrays, slices, and maps. Draws from Effective Go and the major style guides, so the advice is standard practice rather than opinion. Worth having open when you're writing collection manipulation code and want to avoid the common gotchas, especially around JSON marshaling of empty slices and the mutex copying footgun.