Most modern C compilers have used an integrated preprocessor for quite some time, and Clang/LLVM can emit machine code directly without going through a separate assembler.
And, go is built by some of the same people who built C for some of the same purposes (plus some new ones, like concurrency and networks), so it's arguably a "better C", and probably prioritizes some of the same goals. Simplicity and small surface core language area, in particular, but removes some of the dangerous aspects of C (which might be a problem for something performance-oriented, since well-written C is still faster than well-written go for most tasks, and may always be).
But, as you note, if you don't have to build, the cycle is even faster. I still consider a compile phase a slowdown over dynamic languages that don't compile.
Then again, so many people have introduced "compile" like stages into their dynamic process (SASS, LESS, test coverage checks, etc.). It may be difficult to completely get away from a compile like stage in any app of significant size.
Anyway, a large project in go is faster to compile than a large project in C, in my experience, but my experience is exceedingly limited.
Semi-relatedly, the downvoting around here has gotten completely out of control. It's sad, what's happened to HN.
For example, in a recent script I deferred loading the requests module and startup improved a few tenths of a second. Rinse, repeat.
> non-compiled language
C isn't trying to fit in that space. regardless, C code takes far less time to parse, optimise, and convert into machine code than all the languages i know of.
The biggest hold-up in the C world is rampant abuse of #include files.
It's possible to make slow Pascal compilers. But Borland put a lot of effort into that, and it really set a very high standard.
true.
> Nope. Pascal is still king here.
for some values of "king" perhaps - perhaps it's faster to compile, but no arrays of varying lengths in a function call? and if i'm not mistake, a function must be defined before use..? pascal is incredibly restrictive, and perhaps that's why it's so fast.
I'm not going to argue that Pascal is somehow superior to C, it's far more limited, but there's lessons here to be learned on how to make a compiler rip through code.
When I learned C, after a few years of Pascal dialects C just felt like a stone age language.
Well, let's not change the goalpost - your initial assertion was that C has faster compile times. Then chances are that something's got to give, whether that is in the grammar, declaration order, etc.