Go generally compiles so quickly, incremental compilation is unnecessary.
Re:Go Bloviations
by sirclueless on Tuesday September 25, 2012 @09:51AM
(#4570301)
Actually, incremental compilation is the main reason Go compiles so quickly.
Super-fast incremental compilation is the reason they never bothered with parallel compilation.
Go does incremental compilation just fine.
Nobody has bothered to add parallel compilation because building Go code is already so ridiculously fast.
Fast is relative to purpose. Maybe could afford to be faster in the context of an IDE checking your code on the fly, for a large project. I wouldn't know, since I have not attempted to write it.
actually, the Go tool compiles packages in parallel by default.
...under the assumption that something does not depend on too many cgo packages.
Source? That's not what the article says.
The lack of partial/incremental/parallel compilation make this a lot less attractive. A lot of IDE technology (e.g., "intellisense," syntax errors, missing imports) are built off of rapid recompilation.
In fact, doing it any other way seems pretty stupid. If your compiler doesn't offer that information then the IDE has to re-implement those codepaths just to provide that information.