Current features :

1. A small set of generic containers, almost like C++
2. A small set of cross platform API to interact with OS
3. Freestanding (no-libc) if you enable it at compile time
4. I like the current type-safe formatted printing solution
5. Pure C11
6. Compiler errors when working with mismatching types, because of design and usage of the library itself.
7. A set of allocators, very strict on checking for memory errors, each suited for a specific allocation purpose. Almost like Zig.
8. A visionary developer (me ;-)

  
More things incoming. I'm focusing on benchmarking and finding out where I can squeeze more performance, and keep all this transparent and public so it's easier for devs (users) to make decisions on what to do.

  
Note: I started this library way before the git history shows. This library used to live in different projects, and used to be independently available in there, slowly I noticed the pattern that I keep using these so I made this into a library. Because of this, I have spent a significant amount of time experimenting with the design of the library, I have been the first user of it. As time advanced, and my career progressed and I had less and less time to maintain it, I switched to taking help of coding agents to help me prototype my ideas faster, because I already had the clear vision of how I want the code to look. I know many people are skeptical for AI usage in this age and time, but I urge you to take a peek inside code before rejecting on surface. If you find any slop then I'm ready to work with you, but I've given my best to not let any AI slot enter the codebase. I carefully monitor each work to my best extent and I try my best to keep a good standard. There is \`CODING-CONVENTIONS.md\` that I created out of the process of working with coding agents, that might be worth a read if you are interested :-) 

Working On A Type-Safe, Generic Cross Platform, Freestanding C Programming Library