Same here. Yeah, it points to rather poor handling of error condition in this case, and it is an example of deeper problem of terrible error handling in Go, but

Same here. Yeah, it points to rather poor handling of error condition in this case, and it is an example of deeper problem of terrible error handling in Go, but overall - I don't see what the point is. There's plenty of worse code all over the place, in many programs, written in many languages, and this is hardly a notable offender.