C++ Logo

std-proposals

Advanced search

Re: [std-proposals] Benchmarking Including The C++ Standard Library

From: Sebastian Wittmeier <wittmeier_at_[hidden]>
Date: Sun, 17 May 2026 23:58:12 +0200
If compilers start to internally replace #include std header with #import, even old programs profit.   -----Ursprüngliche Nachricht----- Von:Rainer Deyke via Std-Proposals <std-proposals_at_[hidden]> Gesendet:So 17.05.2026 21:40 Betreff:Re: [std-proposals] Benchmarking Including The C++ Standard Library An:std-proposals_at_[hidden]; CC:Rainer Deyke <rainerd_at_[hidden]>; On 5/16/26 22:59, Adrian Johnston via Std-Proposals wrote: > As for floating a proposal on this list, having things like <algorithm-core> > that includes only the contents of <algorithm> as defined by C++11 would be > a way to cut back. I can't say there are any clean and satisfying solutions > that come to mind right now. Giving special treatment to old algorithms is a non-starter for me. Dividing headers by individual symbols (i.e. <all_of>, <any_of>, <none_of>, etc.) I could kind of see, because it actually requires less memorization: the name of the header is always the same as the same of the symbol.  But reorganizing headers at all seems kind of backwards when we have modules. -- Rainer Deyke - rainerd_at_[hidden] -- Std-Proposals mailing list Std-Proposals_at_[hidden] https://lists.isocpp.org/mailman/listinfo.cgi/std-proposals

Received on 2026-05-17 22:00:46