these solutions suffer from the problem that they want too much at once.
-
-
where and how would you place the roots?
-
In my case, box<t> is the type of managed references (like shared_ptr<t>, but GC instead of ARC). There are two types of memory, and the GC treats them differently. References living in unmanaged memory like the stack or C++ heap are roots.
- 6 more replies
New conversation -
-
-
The timeslice for GC assistance can be arbitrarily small. The critical requirement for keeping memory allocation bounded is: on average, the all threads have to free abandoned objects at least as fast as they abandon objects.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I’ll be *very* impressed if you somehow manage to defeat “stop the world” GC curse in multithreaded environment with reasonable perf and RAM cost.
-
intuitively i'd say it's not technically impossible, but i don't have time to do research.
- 5 more replies
New conversation -
-
-
epic purchased rl still servers go down everybody? why?
-
this is not your conversation. go elsewhere.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.