Why does the @golang garbage collector pause all threads to scan the stack? Why not pin stack objects and go 100% nonblocking?
Is there such a thing as a tight loop over heap-allocated objects? Hmm, maybe small linked lists iterated repeatedly.
-
-
Often a compiler could infer lifetime inclusion (a la Rust) as an optimization to pin guaranteed-rooted objects.
-
A lot of graph search algorithms too. But yes, there is some room for inference.
- 1 more reply
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.