3 ms·
Looking over the list I determined that I already regularly follow all the rules but the first three. But, as a C#/C++/Typescript developer, I don't have the f
by emorning3 2y ago
Looking over the list I determined that I already regularly follow all the rules but the first three.
But, as a C#/C++/Typescript developer, I don't have the first clue how any I might go about implementing those rules.
Anybody know of patterns for this kind of safe programming that I can use?
Does just using a language like Zig automatically make my code 'safe'?
Anybody know if generating code from a proof checking language like Lean would satisfy all these rules?
- bluejekyll 2y agoRust pretty much nails all of those.
- nicce 2y agoNot really. By default allocators will panic if there isn't physical memory available. Recursive functions can cause panic at certain depth. Code generated by macros isn't very visible for the developers and recursive macros are very common. Return types are checked only if the developer adds #[must_use]. You can overcome lot if you invest a lot for type system, but that depends on the developer.