Re:Multiple nil types in Go.
by eonil on Tuesday January 07, 2014 @11:22AM
(#7018069)
It's really hard to think the term nil is a value.
IMO, this is a bug in language design. If it's truly a value, I think they should choose a different term rather then `nil` as like they choose `panic/recover` instead of `throw/catch` because they're semantically different.
And also, I really don't know how should I detect nil reliably for an interface type.
IMO, this is a bug in language design. If it's truly a value, I think they should choose a different term rather then `nil` as like they choose `panic/recover` instead of `throw/catch` because they're semantically different.
And also, I really don't know how should I detect nil reliably for an interface type.