frozen
STL
frozen | STL | |
---|---|---|
10 | 154 | |
1,210 | 9,732 | |
- | 1.1% | |
6.1 | 9.7 | |
about 1 month ago | 6 days ago | |
C++ | C++ | |
Apache License 2.0 | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
frozen
-
Making a "constant mapping"
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.
-
Static map - is it possible?
A library exists that can produce constexpr hash table based containers.
-
What C++ library do you wish existed but hasn’t been created yet?
I use the Frozen library for that. Since the conversions should be known at compile time you can make constexpr hash tables for lookups.
-
Command-line util for class implementation (My first try at a professional c++ application)
The constexpr dependency of note here is frozen.
-
Ambition is cute.
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.
-
[Hobby] Bomberman fan 2D Animator needed
Technologies (for curious folks): C++17, SFML, Entt, Frozen, Protobuf, spdlog, GoogleTest, GoogleBenchmark, CMake and Dear ImGui for debug purpose.
-
May 2021 monthly "What are you working on?" thread
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.
-
MSVC Backend Updates in Visual Studio 2019 version 16.10 Preview 2 | C++ Team Blog
This is where I plug Frozen :-] https://github.com/serge-sans-paille/frozen
-
What (relatively) easily to implement features would you like to see in c++23.
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.
-
Compile-time INI config parsing and accessing with C++20
In which case, I believe the answer your question would be yes: the frozen map.
STL
-
Show HN: Logfmtxx – Header only C++23 structured logging library using logfmt
Again, they are barely functional.
MSVC chokes on many standard-defined constructs: https://github.com/microsoft/STL/issues/1694
clang does not claim to be "mostly usable" at all - most papers are not implemented: https://clang.llvm.org/cxx_status.html#cxx20
And gcc will only start ot be usable with CMake when version 14 is released - that has not happened yet.
And, as I mentioned before, IDE support is either buggy (Visual Studio) or non-existing (any other IDE/OS). So you're off to writing in a text editor and hoping your compiler works to a somewhat usable degree. Yes, at some point people should start using modules, I agree, but to advise library maintainers to ship modularized code... the tooling just isn't there yet.
I mean, the GitHub issue is Microsoft trying to ship their standard library modularized, they employ some of the most capable folks on the planet and pay them big money to get that done, while metaphorically sitting next to the Microsoft compiler devs, and they barely, barely get it done (with bugs, as they themselves mention). This is too much for most other library maintainers.
-
Cpp2 and cppfront – An experimental 'C++ syntax 2' and its first compiler
Notice that there are in practice three distinct implementations of the C++ standard library. They're all awful to read though, here's Microsoft's std::vector https://github.com/microsoft/STL/blob/main/stl/inc/vector
However you're being slightly unfair because Rust's Vec is just defined (opaquely) as a RawVec plus a length value, so let's link RawVec, https://doc.rust-lang.org/src/alloc/raw_vec.rs.html -- RawVec is the part responsible for the messy problem of how to actually implement the growable array type.
Still, the existence of three C++ libraries with slightly different (or sometimes hugely different) quality of implementation means good C++ code can't depend on much beyond what the ISO document promises, and yet it must guard against the nonsense inflicted by all three and by lacks of the larger language. In particular everything must use the reserved prefix so that it's not smashed inadvertently by a macro, and lots of weird C++ idioms that preserve performance by sacrificing clarity of implementation are needed, even where you'd ordinarily sacrifice to get the development throughput win of everybody know what's going on. For example you'll see a lot of "pair" types bought into existence which are there to squirrel away a ZST that in C++ can't exist, using the Empty Base Optimisation. In Rust the language has ZSTs so they can just write what they meant.
- C++ Specification vs Implementation
-
C++23: Removing garbage collection support
Here is Microsoft's implementation of map in the standard library. I think of myself as a competent programmer / computer scientist. I couldn't write this: https://github.com/microsoft/STL/blob/f392449fb72d1a387ac502...
-
std::condition_variable wait for (very) long time
Be careful on Windows, the MSVC STL implementation uses the system time, so it can be badly impacted by clock adjustments: https://github.com/microsoft/STL/issues/718
-
Compiler explorer: can you use C++23 std lib modules with MSVC already?
Can you provide a link? If it affects import std;, I'd like to add it to my tracking issue.
- Learn to write production quality STL like classes
-
MSVC C++23 Update
Do you have a list of the bugs you've filed and their current status, like the one I have for the STL? I saw you mentioned 3 bugs 7 months ago, 2 of which were fixed in 17.6 and the third of which was a duplicate of an active bug ("deducing this" is known to not yet work with modules, which is why we don't define the feature-test macro to claim full support).
- C++/CLI wrap of a C++ class that includes <future> in public header
-
Has Boost lost its charm?
Yep. And look at our implementation's name: https://github.com/microsoft/STL
What are some alternatives?
gram_grep - Search text using a grammar, lexer, or straight regex. Chain searches for greater refinement.
EA Standard Template Library - EASTL stands for Electronic Arts Standard Template Library. It is an extensive and robust implementation that has an emphasis on high performance.
parallel-hashmap - A family of header-only, very fast and memory-friendly hashmap and btree containers.
asio - Boost.org asio module
bluebird - A work-in-progess programming language modeled after Ada and C++
robin-hood-hashing - Fast & memory efficient hashtable based on robin hood hashing for C++11/14/17/20
mpv - 🎥 Command line video player
tracy - Frame profiler
c3c - Compiler for the C3 language
gcc
read - A small header-only library to make input in C++ sensible
llvm-project - The LLVM Project is a collection of modular and reusable compiler and toolchain technologies.