alt Hacker News> Also, Fil-C’s guarantee that it will panic on OOB or if a race goes badly
Fil-C as currently implemented does not guarantee panics on unsafe accesses due to races. You dodge the problem by using a private definition of safety under data race that permits program executions nobody would expect.
I define memory safety in terms of capabilities, which is a mainstream definition.
The worst that can happen in a race is that you read or write an object that would have been accessible even in the absence of races.
The thing that makes races hard to debug in C or C++ is memory corruption; that doesn’t happen in Fil-C