Was thinking x86 5-level tables (57 bits) =)
-
-
(For what it’s worth, I think RC was the right choice for Swift, though I prefer GC even for resource constrained environments.)
-
Making gc-managed allocations async, like some of the rust-gc libraries do, might change the game a lot. That could help keep GC managed operations out of non-async C interop or realtime/critical sections
End of conversation
New conversation -
-
-
Haha I just did the initial sketch (and this was before we had a testsuite, when you got to land code "when it compiled"); a much wider cast of long-suffering gecko hackers did all the heavy lifting. But: everything RC I know of that collects cycles does _some_ backup tracing...
-
It's a kinda high-dimensional design space. Peak and steady memory pressure, latency, throughput, fragmentation, code size, etc. All of which are super sensitive to cache and hardware concurrency issues. In RC and tracing/copying regimes, alike. So the ground is always shifting.
- 3 more replies
New conversation -
-
-
"Efficient On-the-Fly Cycle Collection" by Paz et al is a little more recent (2005) and fancier. (Firefox ships an incremental CC, but only single threaded.)
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.