Re:Imposing memory security in C [video]
by johnnyjeans on Thursday February 27, 2025 @12:00PM
(#43196177)
Maybe I just misinterpret what you mean. When you say "no way" and "all cases", I take your meaning literally. The existence of pointers to bypass the borrow checker, disabling runtime bounds checks and unsafe blocks are exactly that: escape hatches to break Rust's safety, in the same way type-casting is an escape hatch to break C's (anemic) type safety, and unsafePerformIO in Haskell is an escape hatch to break every bone in your body.
[ Parent
| on HN ]
Re:Imposing memory security in C [video]
by pizlonator on Thursday February 27, 2025 @01:22PM
(#43196944)
That’s fair.
FWIW, Fil-C’s guarantees are literally what you want. There’s no escape.