The main problem with Go, and this is a deal breaker for me, is that it forces opening curly braces onto the same line, instead of putting them on a line by themselves. This is clearly wrong, and flies in the face of curly good taste.
if (simple_condition) {
} else {
}
for (long and stuffed;
expressions;
here)
{
}
if ((complicated ||
multi_line)
&& condition)
{
}
void function()
{
}
By the way, is grandparent kidding about Go enforcing this?
The only language I can think of which enforces curly brace placement is Awk. (And only in its pattern-action pairs):
BEGIN {
function()
{
if (foo)
{
}
}
}
/regex/ { # can't move this curly to next line
action
} if (simple_condition) {
code;
}
if ((complicated ||
multi_line)
&& condition)
{
code;
}
Simple: it's because in both cases, the "code" follows a previous line from whose first non-whitespace character it indents by the indentation level:
if (...
[INDENT]code
{
[INDENT]code
while (blah
blah
blah) {
code
}
So, rather than dogmatically doing one thing or another, it's better to consider all the alternatives, their relative advantages and disadvantages, and integrate them into an elegant whole.
Go forces one format. Although you definitely can ignore formatting your code and just compile it. It won't fail.
Now I'm wondering if I've just been successfully trolled.