Skip to content

Comment on Multiple nil types in Go.parent

Comments

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.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.