News for hackers. Stuff that matters.
Re:The Year of C++ Successor Languages by worik on Monday January 02, 2023 @03:41PM (#34223368)
How?
Re:The Year of C++ Successor Languages by pebal on Monday January 02, 2023 @03:54PM (#34223511)
By analyzing mutators activity. Only the compacting GCs have to stop the world.
Re:The Year of C++ Successor Languages by worik on Monday January 02, 2023 @08:59PM (#34226581)
Unsure what you mean by "mutators". I am guessing "pointers that can be used to modify data at a memory address"

If so, how can you (as a GC) be sure that while you were adding up all the pointers to an address, and finding none, that another one was not made?

Mystified

Re:The Year of C++ Successor Languages by pebal on Tuesday January 03, 2023 @03:34AM (#34229219)
Mutators are threads that allocate memory and manipulate pointers, they can work completely independently of the GC. A mutator needs only to tag an object when copies or moves a pointer to this object. The GC detects this tag and marks the object as alive. Here is a working implementation for C++: https://github.com/pebal/sgcl
Re:The Year of C++ Successor Languages by aliqot on Tuesday January 03, 2023 @07:58AM (#34230789)
I could listen to you or whoever talk about this all day. Just on the chance you know a good one, do you know any good conference talks or podcasts I can listen to on the same topic?
Re:The Year of C++ Successor Languages by pebal on Tuesday January 03, 2023 @03:14PM (#34237349)
You can watch Herb Sutter talk about deferred_ptr: https://youtu.be/JfmTagWcqoE
Re:The Year of C++ Successor Languages by worik on Tuesday January 03, 2023 @03:01PM (#34237158)
But how can it Markit as dead as the mutatorthread runs?

It must stop the thread surely?

Re:The Year of C++ Successor Languages by pebal on Tuesday January 03, 2023 @03:21PM (#34237420)
SGCL never stops the threads.