Sure all of those are escape hatches that work against any memory safety tech.
replyPoint is, Fil-C goes further than any other memory safety tech in terms of what it guards
How does it compare to the equivalent code in Typescript, Go or C#? Those languages all have “safe” syscall wrappers too, for a subset of syscalls.
replyFully agreed. At some point you have to draw a line and say that the rest is the responsibility of the kernel and hardware and user, and I think Fil-C drew that line in the right place.
reply