3 ms·
There is no possible way for something to be written in 100% memory safe code, no matter what the language, if you include "no unsafe code anywhere in the call
by steveklabnik 2y ago
There is no possible way for something to be written in 100% memory safe code, no matter what the language, if you include "no unsafe code anywhere in the call stack." Interacting with the hardware is not memory safe. Any useful program must on some level involve unsafety. This is true for every programming language.
- no_wizard 2y agoI wasn't asking for 100%, I am asking for a reasonable proof of assertions.
- steveklabnik 2y agoYou may like my next blog post.
- no_wizard 2y agoI think whenever someone takes the time to walk their audience through the nuances of this question its a big win. No different than how I asked of the Go community how it could produce binaries on any platform for all major platforms it supports (IE, you don't have to compile your Go code on Linux for it to work on Linux, only have to set a flag, with the exception If I recall correctly of CGO dependencies but thats a wild horse anyway)
- rc00 2y agoCross-compilation with Cgo can be resolved using something like Zig as the compilation toolchain: https://zig.news/kristoff/building-sqlite-with-cgo-for-every-os-4cic https://zig.news/kristoff/building-sqlite-with-cgo-for-every...