to my mind, of having a type-system.
>>>
>>> P.S. Bug in the snippet given by OP? I expected to see "x != nil"
>>> instead of "x == nil", or else change comments around.
>>>
>>>
>>> On Wednesday, March 23, 2022 at 4:15:13
I barely understand Go, so this is likely a stupid idea. Since Go uses nil
for a lot of things, lots of things can be nil.
I am not a huge fan of the null safe accessor.
( https://github.com/golang/go/issues/42847 )
I am a huge fan of the compiler telling me the places where I have not
checked
