Re:Making C++ Safe Without Borrow Checking, Reference Counti...
by adamnemecek on Friday June 23, 2023 @10:05PM
(#36454750)
There are no Rust crates with 95% unsafe code.
Re:Making C++ Safe Without Borrow Checking, Reference Counti...
by barsonme on Saturday June 24, 2023 @03:34AM
(#36456450)
Crates that only make FFI calls exist. I have written some. :)
Re:Making C++ Safe Without Borrow Checking, Reference Counti...
by kbenson on Saturday June 24, 2023 @03:13PM
(#36461784)
If you think I'm talking about rust vs C and not just using them as stand ins for any language pair, you're not understanding my point because you're too focused on one language in particular, while I'm not focusing on any language in particular.
That's the whole point, it's less about the language, and more about the specifics of the code itself in a testable way. Saying something is written in C without accounting for a bunch of inline assembly is analogous to saying something is written in Rust and not accounting for a bunch of unsafe blocks. Not in that they are equivalently safe or unsafe, but that that high level assumptions because of the language fail because of the practices done within.
If I had to choose between two libraries written in C and one was pure C and one was 50% inlined assembly, and I viewed security and safety as more important for my use case, I know which one I would choose if that information was surfaced to me easily.