3 ms·
I'm pretty sure the problem is Go's use of segmented stacks and runtime, which makes it hard to properly interface with C efficiently.
by dalailambda 10y ago
I'm pretty sure the problem is Go's use of segmented stacks and runtime, which makes it hard to properly interface with C efficiently.
- pjmlp 10y agoSure, but the compiler could generate that FFI code, why the need to rely on an external tool (cgo) and a C compiler?