Robert Jacques wrote:
The thing I thought was unique to Go's compiling/linking was the bypassing of duplicated imports. i.e. If a imported b and c, and b imported c, then compiling a would only link b, since c was included in b's object. They claimed exponential-like speed-up doing this. (If memory of the Google talk serves.)
I think that's a misunderstanding of Go's process. I think Go's compilation process is the same as D's, in that modules only have to be parsed/compiled once regardless of how often they are imported.
The C/C++ #include model is an n squared process.
