inside does not try to derefence the
pointer
to get to a field).
Grepping through our code, I see a lot of pointer receivers on Error
and
String methods (45 and 77 respectively). I think we should at least
change
all of these to be value methods (unless that's not possible. That's
on a nil pointer is totally
fine
and will not panic if the code inside does not try to derefence the
pointer
to get to a field).
Grepping through our code, I see a lot of pointer receivers on Error and
String methods (45 and 77 respectively). I think we should at least
change
all
the pointer to e to access the Message field
which causes the panic. Calling a method on a nil pointer is totally fine
and will not panic if the code inside does not try to derefence the pointer
to get to a field).
Grepping through our code, I see a lot of pointer receivers on Error and
String
if the code inside does not try to derefence the pointer
to get to a field).
Grepping through our code, I see a lot of pointer receivers on Error and
String methods (45 and 77 respectively). I think we should at least change
all of these to be value methods (unless that's not possible. That's
that it is dereferencing the pointer to e to access the Message field
which causes the panic. Calling a method on a nil pointer is totally fine
and will not panic if the code inside does not try to derefence the pointer
to get to a field).
Grepping through our code, I see a lot of pointer receivers on Error
