←back to thread

Go subtleties

(harrisoncramer.me)
234 points darccio | 2 comments | 13 Oct 25 07:42 UTC | HN request time: 0s | source
Show context
valzam ◴[22 Oct 25 09:24 UTC] No.45666643[source]▶
Great list of why one can love and hate Go. I really did enjoy writing it but you never get the sense that you can be truly certain your code is robust because of subtle behaviour around nil.
replies(3): >>45666654 #>>45667227 #>>45671606 #
1. jbreckmckye ◴[22 Oct 25 16:30 UTC] No.45671606[source]▶
As a Go learner, the best explanation that has made sense to me is that interface types essentially just compose two pointers:

P1: The type and its method vtable

P2: The value

Once I understood that I could intuit how a nil Foo was not a nil Bar and not an untyped nil either

replies(1): >>45672977 #
2. whateveracct ◴[22 Oct 25 18:11 UTC] No.45672977[source]▶
ah yes of course - key semantics of `nil` should totally depend on deep implementation details in my language's runtime.

willem-dafoe-head-tap.gif