3 ms·
1. you get spatial memory safety which iirc is more common for security problems than temporal. 2. honestly for high performance applications you might reach f
by throwawaymaths 1y ago
1. you get spatial memory safety which iirc is more common for security problems than temporal.
2. honestly for high performance applications you might reach for an ECS type system anyways (i think dom engines do this) at which point you would be getting around the borrow checker anyways.
- bjackman 1y ago> you get spatial memory safety which iirc is more common for security problems than temporal. No, at least in the Linux kernel use-after-free is the biggest memory safety issue by a long way. Maybe this isn't true in some other system software? Like if you are dealing with parsing. But, you don't really need memory safety for that usecase, fuzzing is unreasonably effective. (Obviously for greenfield dev, safe languages are the way to go. But setting up a dank fuzzing pipeline is easier than migrating to a new language).