For C, which these rules were almost certainly specifically for, these make a lot of sense in eliminating its most common pitfalls.

However, despite C's elegance and simplicity, I can't help but get the feeling that these rules are just a band aid, and that C should not be involved when memory safety is important. Go, Rust, hell, even Racket are probably a better fit for such cases.