checkedc VS stent

https://github.com/microsoft/checkedc

Also, one can combine subsets of C with FOSS, static analyzers that can handle those subsets. Then, compose only in ways that the tools can handle. Then, combinatorial and fuzz testing of the interface composition.

I know you’re doing the project for fun while exploring specific ways to achieve your goals. So, these are just some links and concepts that might help on your journey. Lots of folks don’t know about prior work in this area. So, I keep passing it on.

- [Checked C](https://github.com/microsoft/checkedc) - extensions to make C safer #cpp

Yes. Microsoft Research is working on "Checked C": https://www.microsoft.com/en-us/research/project/checked-c/

As a test, someone ported FreeBSD's networking stack to Checked C. It was easy and there was no overhead to performance and binary size.

Haha. I think they did ultimately agree. Thus a later research project is: Checked-C

In many ways it is up to you to design your APIs to be less verbose. For example, my vector type (from here) looks like:

Minimal version of this concept (but for a Vector) if it helps: https://github.com/osen/stent/blob/master/include/vec.h

Interestingly I developed a "safety" library for C which people later told me followed similar concepts to the double pointer system in classic Mac OS. I arrived at it because I thought it was a fairly good solution.

For C I tend to use a library I wrote called libstent which I have been told is similar to the old memory management approach of classic Mac OS.