I think you're conflating two concepts a little bit - deviation from `gofmt` isn't a compiler error, but lots of things (like unused variables or imports) are. I think they're both great.
Re:Black – Uncompromising Python code formatter
by abtinf on Friday May 17, 2019 @06:47PM
(#19944348)
You are corrrect. I guess I’ve learned to treat deviation from gofmt as error because of the go vim plugin. It runs goimports on save, which fixes a bunch of real errors (like unused imports).
Re:Black – Uncompromising Python code formatter
by masklinn on Friday May 17, 2019 @01:10PM
(#19941535)
> treating deviation as compiler errors.
That's not the case at all. The Go compiler treats an arbitrary few lint issues as compiler errors (e.g. unused imports), code which is not gofmt-formatted isn't a compiler error.
Re:Black – Uncompromising Python code formatter
by lucaspottersky on Friday May 17, 2019 @02:24PM
(#19942187)
thats actually a very annoying feature that has thrown me off when i tried.
you can't even comment out your code while debugging. annoying as hell.
It is immensely valuable to be able to look at any Go code, whether in the toolchain, the standard library, or a random stackoverflow snippet, and not have to think about formatting at all.