I have trust issues because github projects claim to be "lightweight" solutions for X, Y, or Z and then I read the source code.
Näytä tämä ketju
-
Wouldn't it be a fast solution for cases like string lookups? If you're not going to modify it a lot...
Maybe. Not fast compile times. If a project is including memory allocating types from the standard library and claiming to be lightweight, their barometer for “lightweight” is questionable. The unordered_map jab was more of an easy straw man for a joke anyhow.
-
-
Oh, I understand. The STL should come with a "Use with caution" label hahaha
Kiitos. Käytämme tätä aikajanasi parantamiseen. KumoaKumoa
-
-
-
Eh, taking a jab at a project because it uses the STL is unfounded imo. We're slowly reaching the point where we blast people/projects for writing standard C++. As much as I'd like it, forcing people to use EASTL/$alternate_std_lib is not a proper solution to STL compile times.
-
I also wouldn't call for going back to "C with classes". My definition of "light weight" doesn't necessarily include compile times, although it's not a minor factor. I mostly care about the library's runtime profiles wrt memory and speed.
- Näytä vastaukset
Uusi keskustelu -
Lataaminen näyttää kestävän hetken.
Twitter saattaa olla ruuhkautunut tai ongelma on muuten hetkellinen. Yritä uudelleen tai käy Twitterin tilasivulla saadaksesi lisätietoja.