17 ms·
No, the slow part is switching stacks, and coordinating with the scheduler. Go's GC doesn't yet move memory, and even so there will probably be allowances for p
by ominous_prime 11y ago
No, the slow part is switching stacks, and coordinating with the scheduler. Go's GC doesn't yet move memory, and even so there will probably be allowances for passing pointers from Go to C when it is implemented.
- andrewchambers 11y agoThe stacks currently get copied when they run out of space, that may break things already.