Go Error Handling in Practice

This is some real code from Kubernetes repo and it uses lots of errors for each call, does this looks strange or terrible? Is it a good design of error handling in Go? Any better solution?

Using Rust's ? operator might be a better one in this specific case.

  0 COMMENT


No comment available. You can post your comment below.

  POST COMMENT


Sorry! You need to login first to post comment.

OR

  Login with Github


 
0