This is explained in the FAQ: https://golang.org/doc/faq#nil_error
On Tue, 2017-11-14 at 16:37 -0800, Travis Beauvais wrote: > https://play.golang.org/p/76gIgzXgcS > > Why is err not nil when a is? > > Our theory is that err is a pointer to a nil pointer so technically > not > nil. We would have assumed that a pointer to a nil pointer would be > nil > though. Why is that that not the case? > > By the way, we don't need help with this. We found a workaround and > are > satisfied with that. Just looking for details on why this is the case > for > our own knowledge as it tripped us up for a while. > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
