Piero Bosio Social Web Site Personale

@aras libc++ in particular has done good work to factor its headers and generally avoid any of the STL headers from becoming significantly larger from ranges or similar things. Those you only pay for _if you use them_.

Don't get me wrong, ranges as standardized cause _obnoxiously_ slow compile times, and I would generally advise against every including them into code. But you shouldn't pay the price unless you actually include a range header by and large... And if you do, might be worth filing a bug.

@ktf @aras We've seen no meaningful improvements in compile time due to concepts TBH. Not that they're bad for compile times, but most of it doesn't go to extraneous instantiations in `enable_if` that concept checks avoid.

Much more from excessively slow/complex checking of inline function bodies in every translation unit.

@aras This is a big and common thing with C++20.

A bunch of things become constexpr and inline in C++20 is my memory, significantly increasing the cost of the standard library headers in _every_ compile. =[

@dotstdy @whitequark Low-availability of water in locations seems at least reasonably likely to be priced in effectively, and one of the only things that seems likely to be a _consistent_ pressure on DC construction is operational economics.

Definitely will be some cases of super short-sighted sweetheart deals w/ local government combined with unethical DC operators, but even that seems _much_ more likely to occur in harmful ways due to electricity than water...

@whitequark thanks, that matches my take aways from reading other sources, and nice to that from another reader+source perspective. The power / grid side is definitely where it has seemed like the real problems lie here...

@whitequark Would be interested in your key take-aways here -- not sure I can make it through the whole report...