> I don't want to go back to that style because I'm lazy and I'm sure I will forget to handle some errors. Because errors are a returned interface you don't fo

> I don't want to go back to that style because I'm lazy and I'm sure I will forget to handle some errors. Because errors are a returned interface you don't forget to handle them. In fact you have to explicitly tell the language not to handle them by using a _ token on the function call. However it sounds like your argument is more personal preference regarding coding style (eg it seems you tend to favour Sexpression style of syntax over the C-style of syntax) and that's reasonable enough. I do write a lot of code like that too - albeit not in Go.