Anyone claiming they can write memory safe / defined C code at scale either has no experience with it or has their head buried in the sand.
-
-
Or you use a language like Rust permitting you to do stuff like allocation-free parsing via lots of lightweight safe references.
-
It's fine if the compiler tracks the origin of the lifetimes and enforces it. People use C for performance so they will do more.
-
Reference counting can also be done wrong. The Linux kernel gets it wrong all over the place even when reusing code for it.
-
Tools really need to enforce the correct way of doing things. Can have the option of defining new correct mechanisms though.
-
People simply aren't going to get it right without it being enforced. Even if it's a single person and they are really trying.
-
Threads make everything so much harder too. Rust maintains memory safety with threading even while allowing shared mutable data.
-
Threads pretty much have to be forbidden if you want solving the problems to be simple. Otherwise type system needs a lot more.
-
Reference counting has to all be atomic ops with locking mutable data forced unless you have fancy stuff like Send/Sync, etc.
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.