Re:Having fun with Go's nil, interfaces and errors
by prodigal_erik on Saturday September 17, 2016 @07:03PM
(#12522992)
If x.Foo() and y.Foo() do different things and return different values, clearly x != y, and golang needs some kind of SQL-style is-null check rather than using equality to check for null.
But dynamic dispatch on "what type of object do I not have?" is still a damn weird thing to want.
But dynamic dispatch on "what type of object do I not have?" is still a damn weird thing to want.