golang-safety

Prevent nil panics and silent data corruption in Go by applying strict guardrails like safe type assertions, explicit nil returns in interfaces, and defensive nil checks before pointer receiver method calls to stop runtime crashes before they happen.

Your Go code panics when writing to a nil map because uninitialized maps cannot hold values; you must explicitly initialize maps with make before insertion to avoid nil map write panics and ensure safe concurrent access patterns.

Slice append aliasing causes silent bugs in Go when multiple slices share the same backing array after append, meaning modifications to one slice unexpectedly mutate the other; defensive copies prevent this subslice backing-array retention.

The best way to avoid typed-nil interface traps in defensive Go code is to use safe type assertions and return explicit nil values from interfaces rather than returning typed nil pointers that satisfy non-nil interface contracts.

You need to use epsilon-based float comparisons in Go when checking floating-point equality to avoid precision pitfalls, ensuring that silent truncation from integer narrowing conversions and numeric correctness failures are caught during code review.

Yes, defer inside a loop causes resource accumulation in Go because deferred functions only execute when the enclosing function returns; use per-iteration cleanup instead of defer-in-loops to manage resource lifecycles deterministically.