by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 05:35
    kelvin34501 starred mosra/magnum
  • Sep 17 10:27
    Squareys commented #101
  • Sep 16 23:45
    pixelblender commented #101
  • Sep 16 23:45
    pixelblender commented #101
  • Sep 16 19:48
    deiviuds starred mosra/flextgl
  • Sep 16 19:48
    deiviuds starred mosra/magnum-bindings
  • Sep 16 19:47
    deiviuds starred mosra/corrade
  • Sep 16 19:47
    deiviuds starred mosra/magnum-examples
  • Sep 16 19:47
    deiviuds starred mosra/magnum-plugins
  • Sep 16 19:46
    deiviuds starred mosra/magnum
  • Sep 16 14:03
    mosra labeled #11
  • Sep 16 13:09
    Xeverous closed #11
  • Sep 16 13:09
    Xeverous commented #11
  • Sep 16 10:03
    mosra commented #11
  • Sep 16 09:46
    Xeverous commented #11
  • Sep 16 09:30
    mosra commented #11
  • Sep 16 03:22
    inter1965 starred mosra/magnum
  • Sep 15 22:49
    codecov-commenter commented #234
  • Sep 15 20:26
    Xeverous commented #11
  • Sep 15 17:50
    mosra edited #234
Vladimír Vondruš
@mosra
the search data are huge, i need to figure out some better caching
Tracy Ma
@linuxaged
i guessed this may be a network problem, many websites are not accessable here 😔
Vladimír Vondruš
@mosra
i'm hosting this on a local cloud provider in central Europe, which should hopefully be not affected by any political or whatever whims like the US-centric ones are
and also hopefully small enough to be a target of some censorship effort
Vladimír Vondruš
@mosra
anybody using std::string_view?
Vladimír Vondruš
@mosra
asking so i know if i should provide conversion of it to corrade's StringView or if that can wait for later
Tracy Ma
@linuxaged
Corrade container is prefered in our magnum project, lightweight and cross-platform consistent
Janos95
@Janos95
i am using string view, but if corrade provides one I would just switch :)
none of the libraries i am using, uses std string views, so that's pretty easy.
Vladimír Vondruš
@mosra
image.png

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:

Janos95
@Janos95
haha thats pretty morbid
Konstantinos Chatzilygeroudis
@costashatz
Hahahha
Jonathan Hale
@Squareys

does github know something i don't?! :scream:

I think all bigger open source projects are getting this :P

Janos95
@Janos95
just noticed this :
"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)
Vladimír Vondruš
@mosra
hah, i thought you'd compare that to gcc 9
Janos95
@Janos95
I chased the includes and it turns out that <algorithm> transitively includes <ranges> which is 30 loc and contains lots of template stuff
Vladimír Vondruš
@mosra
because this happened for gcc 10, so i expected improvements: https://twitter.com/wakomeup/status/1196097492456214529
#include <ranges> is a fireable offense, then
Janos95
@Janos95
yes I can live without <ranges> in largish projects, but abondoning std::sort etc is not really an options :/
Vladimír Vondruš
@mosra
damn, right
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
Janos95
@Janos95
yes I think one can include
#include <bits/stl_algobase.h>
#include <bits/stl_algo.h>
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:

Janos95
@Janos95

personally even the 0.15 sec was too much for me and so <algorithm> is included almost nowhere in magnum

should I compare compile times?

Vladimír Vondruš
@mosra
of magnum? :D
Vladimír Vondruš
@mosra
you might need to force the -std in CMAKE_CXX_FLAGS, otherwise it'll use 11
Janos95
@Janos95
with DCMAKE_CXX_STANDARD=11 it is 17.43 seconds and with DCMAKE_CXX_STANDARD=20 it is 22.13 seconds. Very unscientific, average of two parallel debug compiles, but variance was quit low, about 0.5 seconds maybe.
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.

Vladimír Vondruš
@mosra
wow, 17 seconds, that's better than i remember
Janos95
@Janos95
yeah it was parallel with 14 cores
Vladimír Vondruš
@mosra
ahah okay
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
Janos95
@Janos95
ah no, no tests. Good point.
Vladimír Vondruš
@mosra
but nobody builds tests except for me, so without them it's the more realistic measurement
with tests it's about 850 ninja targets i'm at 90 seconds and it's getting unbearable
Janos95
@Janos95
a full build with all test takes 26 seconds on 14 cores, one of these newer amd processors will probably eat magnum for breakfast ;). On the other hand it's kind of a bummer if one is not able to work on a laptop anymore...
Vladimír Vondruš
@mosra
that's insane