>Fast Compilation Iron Roads builds quickly, so I can iterate fast, and in this way C has helped my workflow a lot
I wish they'd given a number. 1s?
I dunno how much under a second because my build process only reports durations in seconds.
When using vim with the autocomplete using clang, single file compilations can finish in between keystrokes.
Is there a 0 missing? 6k lines of C is on the lower end of things, especially given how verbose vanilla C can be for basic stuff...
It goes up to 6s when I enable ImGui integration, as ImGui is written in C++.
When I build it with an embedded copy of entire Allegro 5 library, it goes up to 13s.
A fully optimized complete build including both ImGui and Allegro takes 25s. cloc reports 325k lines of code.
During development, most of the time you just compile one unit incrementally, which boils it down to milliseconds either way, so that's probably the figure that's most relevant to your question (although clang-tidy can push it back to a few seconds).
I got tired of that years agao, and have used this approach with success in a few projects: https://www.lelanthran.com/chap2/content.html
I think the most widely deployed mechanism nowadays is protobuf.
Also, I enjoy embedding Lua in projects for extensibility, so this guy is really pulling my heart strings. :-)
I feel like Google's Carbon could be good, but it's still not ready for general use. I'm surprised they even bothered with Carbon since they had built golang for their server software development.
