Sarthak-Pandey commented on PR #21881: URL: https://github.com/apache/nuttx/pull/21881#issuecomment-6937051319
My main motivation was preserving userspace ABI stability: changing public POSIX socket option constants breaks existing binaries, out-of-tree toolchains, and language bindings (like Rust `libc`, Zig, etc.) that hardcode these values against NuttX. However, I understand your concern regarding the memory footprint and CPU overhead of expanding `sockopt_t` to 64-bit on 32-bit architectures. If preserving the 32-bit size is more important for NuttX's embedded constraints than backwards ABI compatibility with external bindings, I'm completely fine with submitting a PR directly to upstream `rust-lang/libc` to update the constants instead. What do you think is the better trade-off for the project? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
