Imposing memory security in C

They say that Rust is going to replace C. I don't believe that and I wanna share how we're doing memory-safe operations in BIRD's C code with no need to enforce this by the language paradigm. It's obviously possible to override that, yet with the right policies and processes in place, it is almost impossible.