> In Go (as in most programming languages) it's not true that the assignment "a = b" implies that "b == foo => a == foo", if a and b are different types. While

> In Go (as in most programming languages) it's not true that the assignment "a = b" implies that "b == foo => a == foo", if a and b are different types. While this is true, in all of those other cases you have the benefit of compile-time type checking so cannot call a function on the wrong type. With nil, you get runtime errors.