4 ms·

I bet there's a ton of Go code out there with methods that assume the pointer receiver cannot be nil without actually checking. The need for the nil checks alon

by khyryk 6y ago

I bet there's a ton of Go code out there with methods that assume the pointer receiver cannot be nil without actually checking. The need for the nil checks along with != err everywhere makes for some incredibly verbose code.

saturn_vk 6y ago
I find that would be a bit pointless. Unless you can actually recover from that, it's better to just panic, since you clearly don't want a nil receiver
- khyryk 6y ago
  Then we're back to the nil interface problem: how do you know whether thing you got is nil or not?