4 ms·
> direct usage of syscalls instead of libc But go isn’t built on top of C? Why would they add more dependencies that complicate and slow down the compilation
by thanatos_dem 8y ago
> direct usage of syscalls instead of libc
But go isn’t built on top of C? Why would they add more dependencies that complicate and slow down the compilation process and hurt portability?
- _ph_ 8y agoNo, by default Go programs and the whole Go toolchain has no C dependencies. The whole Go toolchain is implemented in Go and it doesn't like into any C libraries. Go links against libc only if you either use CGO or a package which has C dependencies, but I am not sure whether there is any package left in the standard distribution, that does.