3 ms·
It's not vapourware: it's called Ironclad C++ and it's on Github. :) https://www.cis.upenn.edu/~eir/papers/2013/ironclad/paper.pdf https://www.cis.upenn.edu/~e
by nickpsecurity 10y ago
It's not vapourware: it's called Ironclad C++ and it's on Github. :)
https://www.cis.upenn.edu/~eir/papers/2013/ironclad/paper.pdf https://www.cis.upenn.edu/~eir/papers/2013/ironclad/paper.pd...
https://github.com/crdelozier/ironclad/ https://github.com/crdelozier/ironclad/
Rust still wins out against it. Yet, a C++ subset with type and memory safety capabilities does exist. The benchmarks look good with conservative GC and all checks on. I vote it as worth consideration for anyone trying to improve C++ app's safety. Might be worth FOSS types improving on if they're sticking with C++.
Edit: Removed link to tool tgat wasnt static. My mistake on that.