As you know I like a lot of the rustix design, the I/O safety, etc. But the "no-libc" path from my use cases I feel brings more risk than reward. One blunt way to look at this is my employer also employs people to work on glibc. We need to support 4 different architectures. The current status quo of using direct syscalls on e.g. x86_64 but libc on ppc64le means that suddenly my software could have ppc64le specific bugs. (And we already have problems with CI capacity on that arch)
Basically, WDYT about exposing use-libc which would turn on rustix_use_libc? (Or is this possible today?)
As you know I like a lot of the rustix design, the I/O safety, etc. But the "no-libc" path from my use cases I feel brings more risk than reward. One blunt way to look at this is my employer also employs people to work on glibc. We need to support 4 different architectures. The current status quo of using direct syscalls on e.g. x86_64 but libc on ppc64le means that suddenly my software could have ppc64le specific bugs. (And we already have problems with CI capacity on that arch)
Basically, WDYT about exposing
use-libcwhich would turn onrustix_use_libc? (Or is this possible today?)