3 ms·
Modules are supposed to make much of this now quite useful info irrelevant. Unfortunately modules are several years in the future, both due to lack of implemen
by gumby 6y ago
Modules are supposed to make much of this now quite useful info irrelevant.
Unfortunately modules are several years in the future, both due to lack of implementations yet and the fact that few projects are being written in C++20 yet. I also harbour a suspicion that tricks like these will still be useful with modules.
- tomovo 6y agoLast time I checked somebody working on modules said something along the lines of "don't expect modules to speed things up". The goals were different, apparently (stop #defines from leaking everywhere, large-project management, libraries). Has this changed, are there any benchmarks available?
- zarkov99 6y agoIf its true that speeding up compilation was not a goal then the committee is out of its mind. Speeding up compilation would have more impact on productivity and the environment than almost anything else that could be done with the language.
- higerordermap 6y agoThe committee was always out of the mind. In the past years they have neglected compile times, debug build performance, error messages or sometimes even performance.
- will4274 6y agoModules contain an optimization (less include leaking) and a pessimization (more serialized build graph). Only the former applies to CPU time, so modules should lead to less cpu time, but it's unclear exactly how that translates to wall time.
- mhh__ 6y agoI still haven't seen a module in the wild yet, they should've been standardized 20 years ago now (D has had modules from day 1, and there are more people on the C++ committee than working on D at all) . I hope they get some traction but I just can't see it helping for all but the newest codebases.
- josefx 6y agoAs far as I understand the issue is basically in the hands of the compiler vendors. They need to have a solution that they can agree on before the c++ committee finalizes it.