Comment on A guide to closures in RustparentComments−bheadmaster3yThe 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...−dontlaugh3yIt does stop me from trying to treat a float as an int. It could have trivially also stopped me from many other mistakes.
Comments
Yes, Go doesn't stop you from making mistakes. I think we've already rehashed that a couple of times...
It does stop me from trying to treat a float as an int. It could have trivially also stopped me from many other mistakes.