Synchronized FFI access to POSIX environment variable functions
@bjorn3 but the main problem here is FFI use cases. A C library wrapped via an FFI binding can call fork/exec, in which case it might use the system environment, not the shadow environment. And if...
View ArticleClik here to view.
Synchronized FFI access to POSIX environment variable functions
bascule: env::remove_var will no longer modify the environment passed to fork/exec I did not suggest to change the behavior of env::remove_var like that, and I would not be in favor of such a change....
View ArticleClik here to view.
Synchronized FFI access to POSIX environment variable functions
josh: As soon as #[deprecated_safe] is available, I think we should use that on the existing functions, and continue having that be our interface to the environment. One issue with deprecated_safe:...
View ArticleClik here to view.
Synchronized FFI access to POSIX environment variable functions
RalfJung: new safety condition Arguably the safety condition has always existed; it's just documented now. Read full topic
View ArticleSynchronized FFI access to POSIX environment variable functions
Arguably this definitely had no safety condition before, since it was a safe function. The fact that this spec was wrong doesn't change that this is the spec we communicated to our users, so cleaning...
View Article