On Thu Jan 30 11:09:57 2025 +0000, Brendan Shanks wrote:
It's a style issue, but `linux` appears a lot in the names of functions, server calls, variables, etc. In theory the ntsync driver could be ported to macOS or FreeBSD, and it would be confusing to be using the "linux" sync functions there. More broadly, maybe it would be clearer to use `ntsync_` instead of `linux_` or `inproc_` (i.e. `ntsync_signal_and_wait()` instead of `inproc_signal_and_wait()`).
I'm inclined to think that non-ntsync code will be eventually phased out to minimize bitrotting code, instead introducing a "dummy" ntsync backend (for older kernels and other OSes) in tandem with the "Linux" ntsync backend. In that perspective, `ntsync_` seems more fit if such code structuring is ever to take place.