-fbounds-safety is awesome!

Here’s what Fil-C gives you that -fbounds-safety doesn’t:

- Fil-C gives you comprehensive memory safety while -fbounds-safety just covers bounds. For example, Fil-C panics on use after free and has well defined semantics on ptr-int type confusion.

- -fbounds-safety requires you to modify your code. Fil-C makes unmodified C/C++ code memory safe.

FWIW, I worked on -fbounds-safety and I still think it’s a good idea. :-)