Why does the @golang garbage collector pause all threads to scan the stack? Why not pin stack objects and go 100% nonblocking?
As if these references were maintained by reference-counting C++ smart pointers.
-
-
Yeah, that's the barrier option. I doubt even go can take 2 ~pipeline flush per stack ref. C++ has by-ref smartptr; go lacks rust's type sys
-
If callers were responsible for pinning parameters, then they could do a simple lifetime analysis and avoid most duplicate pinning.
- 3 more replies
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.