Why does the @golang garbage collector pause all threads to scan the stack? Why not pin stack objects and go 100% nonblocking?
-
-
Uncontended LOCK aren't bad themselves, but they also stall the core. No ILP/MLP for you.
-
I guess you could have ILP, but nothing with a memory operand… That usually doesn't leave much.
End of conversation
New conversation -
-
-
Aren’t you afraid to reach a local optimal dead end by essentially turning C++ into a FP language? These efforts would be for naught then.
-
Eventually FP languages will provide optimization opportunities too complex for imperative ones. The switch will be inevitable and painful.
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.