4 ms·

I think the original claim is that it can be inner nil or outer nil and those are two different things and often you should check for both.

• throwaway894345 5y ago
  The original comment was: > A great innovation of Go is that it includes a built-in reference type with both inner nils and outer nils. Which the OP later clarified by saying an interface can be both nil and not nil at the same time. So it’s pretty clear that we’re debating about whether interfaces have three states (nil, valid, and both) i.e., multiple kinds on nullity (inner vs outer).
  • anonymoushn 5y ago
    > Which the OP later clarified by saying an interface can be both nil and not nil at the same time. I don't think I made any such clarification...
    • throwaway894345 5y ago
      You aren’t the OP. I was referring to this: > typed nils are a single value which is both nil and non-nil at the same time.
      • anonymoushn 5y ago
        the "original poster" is someone other than the person who made "the original comment"?"