frozen VS read

I found this extension that implements "frozen" versions of some C++ containers, but I was wondering if there is a good solution available in the standard library.

A library exists that can produce constexpr hash table based containers.

I use the Frozen library for that. Since the conversions should be known at compile time you can make constexpr hash tables for lookups.

The constexpr dependency of note here is frozen.

In C++, a drop-in replacement for your DSA can provide significant improvements over the standard library. Particularly the standard unordered_map class can be improved by 50% to 100% (e.g. https://github.com/greg7mdp/parallel-hashmap, or for static maps https://github.com/serge-sans-paille/frozen). Of course, recognize that creating a DS/A from scratch is an entire project, and you shouldn't roll your own for an independent codebase.

Technologies (for curious folks): C++17, SFML, Entt, Frozen, Protobuf, spdlog, GoogleTest, GoogleBenchmark, CMake and Dear ImGui for debug purpose.

In the language, I added anonymous array literals. I did some cleanup in the compiler and updated to LLVM 12 from 10 (which was pretty trivial, surprisingly). I also added frozen, a C++ perfect-hashing library, as a dependency to speed up the lookup of keywords in my lexer. The library exploits C++’s constexpr features to generate a perfect hash at compile-time without any separate build step, which is great, and it also provides a drop-in replacement for std::unordered_map that uses the hash.

This is where I plug Frozen :-] https://github.com/serge-sans-paille/frozen

I’ve no idea how hard it is to implement, but return type polymorphism would be nice. Especially returning different things based on the constexpress of the result. And then add Frozen eqivalents of associative containers to the STL, so that, for example constexpr auto set = std::make_set(...) would be frozen::set, and auto set = std::make_set(...) would be std::set.

In which case, I believe the answer your question would be yes: the frozen map.

It was on the mailing list that screens proposals prior to writing papers. Basically it was for making input much easier to work with, like this: https://github.com/ShakaUVM/read

I have thought about submitting a library of mine (https://github.com/ShakaUVM/read) for standardization or inclusion in Boost. Basically it does for input what format did for output - replace the stream system with something more functional.

Using readlib:

That's why I wrote my read library (https://github.com/ShakaUVM/read). You can just do:

5) Make input come from functions rather than call by reference, such as what I did here: https://github.com/ShakaUVM/read