4 ms·

Pretty sure you can just disable leak checking.

• 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 ago
    You 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.
    • dajtxx 1y ago
      It can still be a bug if you use something after you would have freed it because your code isn't meant to be using that object any more. It points to errors in the logic.
      • guerrilla 1y ago
        Agreed. I think being methodical is better here for sure.