> I think it is fair to call C "unsafe" given the above definition of safe/unsafe. I don't think anyone would disagree with this. What they're saying is that a

> I think it is fair to call C "unsafe" given the above definition of safe/unsafe. I don't think anyone would disagree with this. What they're saying is that a segfault is safe and that's because a segfault is essentially your OS's version of an out-of-bounds error, one of the reasons that C is not safe is because an out-of-bounds access will not necessarily cause a segfault.