Null pointer panics rarely happen where the null is introduced. Instead the null propagates somewhere else where you assume non-null, and you get the panic the

Null pointer panics rarely happen where the null is introduced. Instead the null propagates somewhere else where you assume non-null, and you get the panic there. That's bad error reporting, and it only happens because Go lacks a proper nullable/option type.