>>30
The boilerplate is required. Take exceptions (I found the link):
http://groups.google.com/group/golang-nuts/browse_thread/thread/1ce5cd050bb973e4
The boilerplate required is fairly small (there are worse cases, like dealing with arrays of channels), but the code is far more ambiguous than traditional exceptions handling mechanisms. I'd rather write twice as much and have clear code, which is rarely possible. (The same problem arises with FSMs, arrays of channels and so on.)
I enjoy the fact that they're building features out of the language; the problem is this isn't Perl so you can't just
use Exceptions; and have a syntax that supports you. Instead you've got the machine bits all over the floor, and it's not clear to an onlooker whether they are part of one machine or part of another.