logoalt Hacker News

n42today at 1:39 PM1 replyview on HN

Not if choosing statically checked memory safety sacrifices for correctness where it is a local optimum


Replies

Ygg2today at 3:58 PM

If you sacrifice memory safety for correctness, that just means it's not correct. If safety is crucial, it must be safe under all inputs, and if there are data races.

It's a bit like saying, "Yeah, our system is safe, but if there are two threads racing or use after free somewhere, then all bets are off."

show 1 reply