It's arguably more error-prone, e.g. Rob Pike justifies Go's decision to use curly braces like so: >Some observers objected to Go's C-like block structure with

It's arguably more error-prone, e.g. Rob Pike justifies Go's decision to use curly braces like so: >Some observers objected to Go's C-like block structure with braces, preferring the use of spaces for indentation, in the style of Python or Haskell. However, we have had extensive experience tracking down build and test failures caused by cross-language builds where a Python snippet embedded in another language, for instance through a SWIG invocation, is subtly and invisibly broken by a change in the indentation of the surrounding code. Our position is therefore that, although spaces for indentation is nice for small programs, it doesn't scale well, and the bigger and more heterogeneous the code base, the more trouble it can cause. It is better to forgo convenience for safety and dependability, so Go has brace-bounded blocks.