Error Handling #2 about golangtraining

[riscie]

I saw this recommendation before @amanuel2
Have to say I like it the way todd does it, because it does not hide our error handling. When reading code I can read what we do when an error occurs which often is quite important. Works better with my reading flow also.

In the end it's a matter of style i guess.

[apkrieg]

You wouldn't always want to panic when handling errors. In simple example apps there is no need to recover from a failure, but when you are developing an application that has real-world purpose you would want to handle and recover from errors. So you would recover in the if statement. If you really want to use the check function you could maybe modify it like this:

func check(e error, callback func(e error)) {
  if e != nil {
    callback(e)
  }
}

and then handle errors like this:

check(err, func(e error) {
  tryAgain()
})

Hope this helps :)

[amanuel2]

Yea @apkrieg you can manupilate it how you want it. But im just asking if you guys want to change it so there isnt a

if e!=nil{
//DoStuff
}

Just make a function so it dosent get repetitive and its good/clean code.