alt Hacker NewsI guess to get on board with this, it is my understanding you have to accept the premise of a Garbage Collector in the runtime?
Replies
thomasmg • yesterday at 6:00 PM
The author of Fil-C does have some ideas to avoid a garbage collector [1], in summary: Use-after-free at worst means you might see an object of the same size, but you can not corrupt data structures (no pointer / integer confusion). This would be more secure than standard C, but less secure than Fil-C with GC.
kragen • yesterday at 11:24 AM
So far we haven't found a viable alternative; CHERI has holes in its temporal integrity guarantees.
➕ show 1 reply
Note that it is a garbage collector designed and implemented by one of the most experienced GC experts on earth. He previously designed and implemented WebKit's state of the art concurrent GC, for example. So—yes, but don't dismiss it too quickly.