Comment
Comment by nemothekid
You can hit this bug without using reflect. It, to me, is Go's third biggest wart. I'm particularly fond of this bug, because I got bit by it and it crashed prod during an important sales demo.
This is the "nil interface" trap and will crash with an NPE even though are "checking" nil.