4 ms·
I'm no kernel developer, but I would guess that even putting some yellow caution tape around the risky stuff, and knowing everything that isn't taped off is les
by mumblemumble 5y ago
I'm no kernel developer, but I would guess that even putting some yellow caution tape around the risky stuff, and knowing everything that isn't taped off is less risky, could be a win for maintainability. The current status quo is presumably that people need to be able to grok 100% of the code deeply enough to be able to evaluate all proposed changes for memory safety implications at all times.
- johnisgood 5y agoThe problem is that unsafe blocks affect the code outside it, too. It is a common misconception that it does not.
- mumblemumble 5y agoBut can't you at least surmise that, as long as you can independently show that the code in the unsafe blocks only affects safe code in the intended manner, you can reason about the unsafe behavior in a more modular way? Kind of a memory safety equivalent to what structured programming did for control flow.