Hands-On Microservices with Kubernetes

Checking errors

One of the annoying things about Go is the explicit error checking you have to do all time. The following snippet is very common; we call a function that returns a result and an error, check the error, and if it's not nil, we do something (often, we just return):

... result, err := foo() if err != nil {     return err }...

The Check() function makes this a little more concise by deciding that it will just panic and exit the program (or the current Go routine). This is an acceptable choice in a testing scenario where you want to bail out once any failure is encountered:

func Check(err error) { if err != nil { panic(err) } }

The previous snippet can be shortened to the following:

... result, err := foo() Check(err)...

If you have ...