3 ms·
Why is this a nothingburger? If you're making the claim that it's safe and it actively leaks memory, how do we know it doesn't also allow buffer overruns or dou
by _gabe_ 4y ago
Why is this a nothingburger? If you're making the claim that it's safe and it actively leaks memory, how do we know it doesn't also allow buffer overruns or double frees?
It would be nice if you allowed an option to compile with memory tracking so that as a user of the language you can debug this sort of stuff to make sure it's not a big deal waiting to happen.
- amedvednikov 4y ago800 bytes in some GC cleanup is not "actively leaking memory". It's a nothingburger. We know it's not a big deal, we have lots of valgrind tests running on CI. And we have V web services running for months and not leaking memory.