Go discourages it http://golang.org/doc/effective_go.html#if http://golang.org/doc/effective_go.html#if I think a blanket ban on multiple return locations is s

Go discourages it http://golang.org/doc/effective_go.html#if http://golang.org/doc/effective_go.html#if I think a blanket ban on multiple return locations is silly, as they can often be used to simplify code. There may be times when setting a return value is preferable, and I think you should use your judgement there. http://stackoverflow.com/questions/36707/should-a-function-have-only-one-return-statement http://stackoverflow.com/questions/36707/should-a-function-h...