and also hopefully small enough to be a target of some censorship effort
none of the libraries i am using, uses std string views, so that's pretty easy.
An appointed successor can manage your public repositories after presenting a death certificate then waiting for 7 days or presenting an obituary then waiting for 21 days.
does github know something i don't?! :scream:
"echo "#include <algorithm>" | gcc-head -std=c++11 -P -E -x c++ - | wc -l" returns 11765
while
"echo "#include <algorithm>" | gcc-head -std=c++20 -P -E -x c++ - | wc -l" returns a whopping 45222
compiling an empty file including the algorithm header takes 0.15 sec (with c++11) vs 0.9 sec (with c++20)
because this happened for gcc 10, so i expected improvements: https://twitter.com/wakomeup/status/1196097492456214529
#include <ranges> is a fireable offense, then
i was just about to ask what exactly do you need from there
isn't it in some utility / internal header on gcc? so i could do another
Utility/StlMath.h "deshittifier" but for <algorithm>
personally even the 0.15 sec was too much for me and so
<algorithm> is included almost nowhere in magnum
another option: don't use c++20 :D
not sure about other platforms
another option: don't use c++20 :D
but I already changed all my enable_if's to requires clauses :laughing:
but interestingly it is about 1.5 slower than my system gcc, maybe I messed up compiling gcc, so everything with a grain of salt.
you might need to force the -std in CMAKE_CXX_FLAGS, otherwise it'll use 11
ah ok, I'll check one moment.
people with fast machines
was it with all tests?
or just the libs
libs alone i remember were around 20 seconds last time i checked, on a 8-core machine
with tests it's about 850 ninja targets i'm at 90 seconds and it's getting unbearable