Written by someone who (apparently) thinks that a simpler malloc will solve memory safety issues, someone apparently unaware of the dangers of pointers arithmet

Written by someone who (apparently) thinks that a simpler malloc will solve memory safety issues, someone apparently unaware of the dangers of pointers arithmetic, out of bounds indexing/references, uninitialized values, UB, etc. (Don't misunderstand me, I will happily - and carefully - program in C when I need to, or can, and will claim to be a safe three star programmer (the only time I had to do it, which was recently, I spent a LOT of time making sure it was necessary and safe), but the reason I can write reasonably safe code in C is that I know where (at least some of) the foot guns are - and every time I do something close to the edge, I learn of more limb shredding behaviour. But I am slowly acquiring Rust, and some of my colleagues are much farther along that path. For what we do, some things MUST be done in memory safe languages, and the Rust I've read and written is such a joy compared with the pain I often feel when using a language I have love for (takes out fingers, counts) more than 4 decades. The idea of NOT having to spend hours trying to find that unexpected leak or SEGFAULT is giddy-making.)