3 ms·
But for example verifying that memory is not touched after it is supposed to, is much harder when you can't rely on it being freed. Of course literally running
by 1718627440 1y ago
But for example verifying that memory is not touched after it is supposed to, is much harder when you can't rely on it being freed.
Of course literally running valgrind is still possible, but it is difficult to get useful information.
- nick__m 1y agoYou cannot have use-after-free if you never call free, so there are no points at which memory should not be touched. That's the beauty of the never free memory management strategy.