Many of their TOCTOU issues are something a type system can help with. Require operations to execute on a fd handle directly rather than using convenience functions.

let fd = FileDescriptor::new(path);
fd.delete()?;
fd.create(mode)?;

let is_root = fd == FileDescriptor::new("/"); // does (dev, inode) comparison internally
// etc

The uutils devs would need to create that themselves, but OpenOptions seems to get them part of the way there at least.

Java and similar (i.e. c#) are memory safe and run on garbage collected runtime.

@davidgro @hunger Last basic variant I worked with was the basic of the commodore machines. It had no NULL. I have also seen vbscript a little, afaik also it had not.In Java, null does not mean a real 0 value, I think it is more like a static const, more similar to the None type of the Python. Its name is only a helper for the C/C++ guys to better understand a stack trace.

A null does not make it memory unsafe. You aren't accessing invalid memory, the runtime just raises a NRE. Which is fine. No memory safety violated.

Java is, as long as you stick to pure java and not native interop, entirely memory safe. And that's achieved by giving up control of memory allocation to the garbage collector.

Rust is not the first memory safe language. It does however, manage to achieve memory safety without needing a garbage collector. Which is what drew my initial interest.

@davidgro @hunger Learn the three languages you are talking about before talking about them. Ill-informed thoughts impress no one.