What misuse are you imagining that isn’t a memory safety problem?
replyYou might find that Fil-C prevents those too. It’s pretty strict. You can only use longjmp to pop stack like an exception would
Resource leaks, crossing non-exception-safe library/system code, CPU-specific quirks like accidentally unrestored FP/vector/control state, etc. Granted it's always been highly system-specific stuff, but that's the worst kind.
replyGotcha, that’s a good list.
replyIt’s true that Fil-C doesn’t try to protect you from those bugs. I just don’t think of those as the worst things that can happen when you misuse these APIs.