Date: Tue, 26 May 2026 14:20:16 -0700
Simply calling *fork()* in the compiler was my favorite response so far. If
the world moves towards *import std;* everywhere I think the case for that
becomes compelling.
Again, my original point on this mailing list was just that there is a cost
to adding more and more to the same headers with every version of the
standard. I provided this benchmarking data because I was asked and I am
also interested in experimenting with the latest C++ features.
I still feel strongly about having instantaneous build times, but not
everyone has to agree. Just for comparison my non-allocating stripped down
version of the standard loads as a module and creates a simple object
output in 16ms instead of 50ms. And that module has twice as much
functionality as I would ever use.
the world moves towards *import std;* everywhere I think the case for that
becomes compelling.
Again, my original point on this mailing list was just that there is a cost
to adding more and more to the same headers with every version of the
standard. I provided this benchmarking data because I was asked and I am
also interested in experimenting with the latest C++ features.
I still feel strongly about having instantaneous build times, but not
everyone has to agree. Just for comparison my non-allocating stripped down
version of the standard loads as a module and creates a simple object
output in 16ms instead of 50ms. And that module has twice as much
functionality as I would ever use.
Received on 2026-05-26 21:20:28
