4 ms·
The higher overhead of talking to C from Go (as compared to C#/Java) has not changed, and likely won't. And of course, C# and Java also have overhead.
by gameswithgo 7y ago
The higher overhead of talking to C from Go (as compared to C#/Java) has not changed, and likely won't.
And of course, C# and Java also have overhead.
- buybackoff 7y agoI mean talking to Go from C or any other language as if Go was replacing a C library. Could not find low-level detail on this, but I remember it used to be very slow. E.g. PInvoke has an overhead of between 10 and 30 x86 instructions per call, which is quite small. Actually I'm not sure if that is possible now to call Go from C via some C ABI/ABI. I looked into CGO in the past.
- proyb2 7y agoAlternative to Go, the ease of talking to C could get simple, V language which transpile into C code with minimal overhead, still infancy at this stage, the end goals is to translate C source to readable V code. https://vlang.io https://vlang.io