Re:On Go, Portability, and System Interfaces
by 4ad on Tuesday September 22, 2015 @08:16PM
(#10262608)
Not sure I understand your point, tcsetattr calls a system call on its own...
So the alternatives are between doing a trivial system call on the Go stack, or doing a complex stack switch operation that does the (too complicated) System V calling convention ABI translation, and then calls a function that does a system call...
Even worst case, if calling overhead is a problem, the Go team can likely improve it at some point, but they are less likely to magically map special cases of syscall.SYS_IOCTL to tcsetattr for the sake of portability.