5 ms·
>"golang also targets syscalls instead of the C standard library" What would have been the reasons for targeting syscalls directly instead of the C standard li
by bogomipz 10y ago
>"golang also targets syscalls instead of the C standard library"
What would have been the reasons for targeting syscalls directly instead of the C standard library?
- aduffy 10y agoI'm guessing it has to do with the fact that you can build go binaries not linked with libc, they also expose syscall.RawSyscall anyway that all the other syscall wrappers call out to last time I looked
- masklinn 10y ago> What would have been the reasons for targeting syscalls directly instead of the C standard library? Since the standard library probably assumes (and requires) a C stack, linking against the standard library would require cgo (or some other specific workaround) on non-linux platforms.