What I was referring to is curly brace placement.
func main() { }
vs
func main() { }
which produces the error "prog.go:4: syntax error: unexpected semicolon or newline before {". As I understand it this is because of the rules of where it will insert semicolons. It isn't enforcing everything about the format which is why I said "to a degree" but it is still one of the most opinionated compilers on format that I know of.
Either way, I'm glad they did it. The "where should the curly brace go" is one of the most annoying bike-sheds.
In case anyone else thinks they're insane, the two are the same. The second one should have been
func main()
{
}Oh thanks! Not sure how it got trashed.
Re:Jsfmt – Like Gofmt, but for JavaScript
by jzelinskie on Friday May 09, 2014 @10:11PM
(#7724219)
How automatic semi-colon insertion works causes braces to be on the same line as a function signatures/ifs/switches/etc.
This program won't compile: http://play.golang.org/p/8DSev4ZjWZ
Given that, jsfmt doesn't need 100% adoption: using it in a single project or library would still be useful. Stating new contributions must be jsfmt'ed would be less trouble than most standard pull request requirements (pass + update any relevant testing code, ...).
I personally love these formatting tools and am looking forward to more of them, such as ClangFormat[1].
* You might be thinking of unused variables or imports resulting in compiler errors, which isn't the same as not compiling due to formatting?
[1]: http://clang.llvm.org/docs/ClangFormat.html