cons-cat/libcat

🐈‍⬛ A runtime for C++26 w/out libC or POSIX. Smaller binaries, only arena allocators, SIMD, stronger type safety than STL, and value-based errors!

libCat 🐈‍⬛

libCat is a non-POSIX compliant C++26 runtime. It has no pthreads nor malloc(), and by extension no exceptions. It has type-safe arithmetic, SIMD, fast syscalls, interfaces (also known as facades), hierarchical memory allocators, and value-based error-handling, among many other features.

http://wgoo.ch/overflow.html

https://youtu.be/BrBb0mqoIAc

More essays and videos will come in the future.

Building

libCat requires a development version of GCC 15 from the trunk branch. Compiling libCat is only tested using ninja. Configuring the build requires CMake 3.29.

$ cmake -B build/ -G 'Ninja Multi-Config' # or: cmake -B build -GNinja
$ cmake --build build/  # or: ninja -C build/
$ ./build/tests/Debug/unit_tests

The .clang-format and .clang-tidy configurations are only compatible with recent builds of clang-tools from the main branch.

libcat's Issues

How about less restrictive license?

Hi,

I'm considering development of my next Commodore Amiga game using C++, but unfortunately the prominent distribution of bleeding edge GCC in our community lacks STL and most of stdlib. So, I'm looking for a replacement, and this one looks like it could do the job! If it works with reasonable performance, which I think it will, I'd probably end up endorsing this library to be used in tandem with my Amiga gamedev library/framework, which I'm developing for 10 years now.

Unfortunately, linking with GPL (or Affero GPL) requires making the remaining code on similar license, which is kinda no no for me - I'm all for open source, but forcing such license discourages some commercial scenarios, unfortunately - speaking plainly, you can't keep your game closed source while using open code, which is something some of my users prefer doing.

So, how about using some lightweight, less viral license with less text and caveats? If you want people to share their modifications back, MPL2 could be a good choice. If you just prefer attribution, MIT/BSD would be just fine. Or is it GPL because your code borrowed something GPLy from other source?

Thanks for considering it!