Please include: Project name and description (if not widely known); Tech stack; Areas needing help (DOCS, CODE, DESIGN, etc.); Level (BEGINNER-FRIENDLY if applicable); Email address or other means of contacting you.
Ground rules:
Post only if you maintain/run the project
One post per project/suite
No commercial recruitment
No thread complaints
Developers: Only reach out if you actually want to contribute.
Written in C and C++.
Need most help just porting C programs to Fil-C. Often porting is as easy as recompiling, but sometimes there are compatibility issues to resolve similar to if you were porting C code to a new CPU or OS. Could also use help with compiler hacking (llvm expertise required) and runtime hacking (experience with high level language runtimes required).
I don’t think it’s possible to catch all use after frees at compile time precisely. Like, you could have a checker that catches all errors but also rejects valid programs or you can have a checker that accepts all valid programs but doesn’t find all the bugs. To be precise it has to be at runtime, and that’s what Fil-C does.
In Fil-C, if you don’t like the use after free panic, then just don’t call free and let the GC free your objects.
And if you’re doing safety critical stuff (I’m assuming that’s what you’re getting at) then the game is to prove that the system will be safe in the sense of not hurting people, not in the sense of memory safety. And that proof burden is much higher than the proof burden for memory safety.