ctl

Well, I do like mine better, which is closer to the STL, and for all containers. https://github.com/rurban/ctl/

search for htable or hashtable in thousands of open source projects. only a minority has worse hashtables than this one (clisp, perl5 e.g.). For better ones I would point to my linked list implementation: https://github.com/rurban/ctl/blob/master/ctl/unordered_set.... (because it has various security policies, nobody else has) or https://github.com/LIMachi/swiss-table (all in C)

mine is better :) https://github.com/rurban/ctl/

There's also a CTL fork that might be of interest: https://github.com/rurban/ctl

I favor the CTL over the STL anytime, because it compiles much faster, is much smaller, no indirect vtable calls, no bloated god objects, has no magic hooks attached, like dereferencing refs and ops, is clear on stack vs heap allocation. The downside of course is that generics and iterators on those are a bit more troublesome, only compiler dependent goodies (mostly only clang, not gcc), like overloads or constexpr. C++ templates are ugly, and the STL is very buggy and limited. Also no security and no performance. They started on the wrong foot and had to keep it there. Rust has an annoying syntax, but a much better library culture. https://github.com/rurban/ctl

Can I use that with GitHub actions? I have some crazy slow C/C++ build times with O2 and asan, which usually leads to g++ timing out. Not just 40min build times. Some huge autogenerated testcases to cross-test all iterator combinations against C. I'd really need -O3 for -finline, but -O2, -O3 and -Ofast all fail too build. Splitting it up didn't help. So far I went with #pragma optimize O1. https://github.com/rurban/ctl/actions/workflows/master.yml C++ templates are the worst. The pure C variant builds in seconds. I pity all C++ folks

Similar to mine https://github.com/rurban/ctl But mine are very close to the STL with generic iterators/ranges and algorithms over containers.

KLEE is only popular with the HN crowd, but not certainly not in the industry. There cbmc/satabs is leading. Esp. automotive. Also much older, and much easier to use. I recently even added formal verification to my CTL library variant, the STL for C. https://github.com/rurban/ctl/commit/cc65e82ba1fdafcf9c83697... cbmc found some huge bugs the testsuites were not able to find. KLEE has similar status as Z3. Hugely popular, but rarely used in practice. Educational toys, or used in side-projects only.

Yet another glib, a STL for C, which is header-only, complete, tiny and sucks much less. https://github.com/rurban/ctl

I didn't like the names at all, and also it shouldn't be in the main namespace, but under ctl/ https://github.com/rurban/ctl In work are map, forward_list, unordered_set, and utf-8 support for strings and identifiers, with its stricter rules.