There's this increasing tendency to talk about memory safety as if, because it's the most pressing problem _right now_, solving it means you've won the battle. But that's not the end goal… it's the start. Literally the least you can do.
Conversation
Notices
-
Embed this notice
Ben Cohen (airspeedswift@mastodon.social)'s status on Sunday, 15-Oct-2023 00:17:06 JST Ben Cohen - Paul Cantrell repeated this.
-
Embed this notice
Ben Cohen (airspeedswift@mastodon.social)'s status on Sunday, 15-Oct-2023 00:17:06 JST Ben Cohen Percentages add up to 100. As segfaults and exploits due to buffer overruns or use-after-frees decrease, the proportion of bugs that come down to logic errors will increase.
If the way you achieved memory safety (or performance) means your code is so ceremony-heavy that it starts to impact correctness, because you can't so easily see what it is actually trying to _do_, this is unfortunate.
Think about this now, not once we get there.