3 ms·
> The problem with nil for any pointer or interface is that you can compile code dereferencing it without first checking if it's nil. Yes, Go doesn't stop you
by bheadmaster 3y ago
> The problem with nil for any pointer or interface is that you can compile code dereferencing it without first checking if it's nil.
Yes, Go doesn't stop you from making mistakes. I think we've already rehashed that a couple of times...
- dontlaugh 3y agoIt does stop me from trying to treat a float as an int. It could have trivially also stopped me from many other mistakes.