News for hackers. Stuff that matters.
Re:For Better Computing, Liberate CPUs from Garbage Collection by rayiner on Thursday May 09, 2019 @12:40PM (#19869778)
> When you say "manual memory management" if you're thinking C-style malloc-free then you have a point, it's very easy to forget a free() somewhere. But any language with destructors can handle these situations without much more overhead than GC-based approaches.

What happens when that object is shared and still referenced from somewhere else? Now you have a use after free error waiting to happen.

Re:For Better Computing, Liberate CPUs from Garbage Collection by Shikadi on Thursday May 09, 2019 @03:19PM (#19871319)
That's what smart pointers/ref counting is for
Re:For Better Computing, Liberate CPUs from Garbage Collection by tptacek on Thursday May 09, 2019 @03:52PM (#19871684)
C++ is the flagship language for smart pointers and UAF memory corruption flaws are endemic to it.
Re:For Better Computing, Liberate CPUs from Garbage Collection by rayiner on Thursday May 09, 2019 @05:52PM (#19872801)
Re:For Better Computing, Liberate CPUs from Garbage Collection by tjoff on Saturday May 11, 2019 @03:18AM (#19885030)
Doesn't seem related though?

Unless you want to pick on the specific implementation?

Re:For Better Computing, Liberate CPUs from Garbage Collection by UncleMeat on Friday May 10, 2019 @07:02PM (#19883092)
That's literally GC.