Googleのコーディング規約で例外つかわないとあったが、
Goもないんだな

> Why does Go not have exceptions?
>
> We believe that coupling exceptions to a control structure,
> as in the try-catch-finally idiom, results in convoluted code.
> It also tends to encourage programmers to label too many ordinary errors,
> such as failing to open a file, as exceptional.

> Go takes a different approach. Instead of exceptions,
> it has a couple of built-in functions to signal and recover from truly exceptional conditions.
> The recovery mechanism is executed only as part of a function's state being torn
> down after an error, which is sufficient to handle catastrophe but requires
> no extra control structures and, when used well, can result in clean error-handling code.

> See the Defer, Panic, and Recover article for details.


FAQ - The Go Programming Language
http://golang.org/doc/go_faq.html