Jacob Lifshay
Jacob Lifshay
> I agree with @tschneidereit. The goal of the filesystem APIs is to enable access to filesystems, so we have to work within what they give us. So we can't...
oops... closed by mistake
if you ignore the difference between real uid/gid and effective uid/gid (the distinction is mostly only useful for programs like `sudo`), then yes you should be able to implement it...
maybe there should be a `RwLockTryUpgradeableReadLock` which allows multiple locks simultaneously and `RwLockUpgradeableReadLock` which allows only one lock at a time.
> In particular, could you show that the performance is actually _substantially better_ than dropping the read lock and then acquiring a write lock? that's not a replacement for upgrading...
note that nodejs has functions for async writes to stdout/stderr. also, on unix it's common for commands to write binary to stdout, e.g. writing a raw gzip file to stdout:...
i was just discussing [`SIGPIPE` issues on another project](https://github.com/rust-lang/rust/issues/125418#issuecomment-2718734548), so sounds good to me, assuming you can get good handling for what to do when the read end of `stdout`...