]> git.lizzy.rs Git - rust.git/commit
Auto merge of #24741 - cgwalters:note-setenv-and-unsetenv-are-not-threadsafe, r=alexc...
authorbors <bors@rust-lang.org>
Thu, 14 May 2015 07:15:51 +0000 (07:15 +0000)
committerbors <bors@rust-lang.org>
Thu, 14 May 2015 07:15:51 +0000 (07:15 +0000)
commit0a1a53d6933b53b804269ce236760847c5dd00fa
tree62c6473f672213d5db737ffb671291d583b3080e
parente77b03d783b5c9df88f1f743fe29615db43e1dda
parent44a5bf1b7d8d16e73ab5631c4dd6bd5107079c5f
Auto merge of #24741 - cgwalters:note-setenv-and-unsetenv-are-not-threadsafe, r=alexcrichton

See:
https://sourceware.org/bugzilla/show_bug.cgi?id=4887#c9
https://bugs.freedesktop.org/show_bug.cgi?id=65681

I just noticed this while talking to someone who was using
`os.environ['FOO'] = 'BAR'` in Python and since I'm learning Rust, I
was curious if it did anything special here (and the answer appears to
be no).

Java got this right by disallowing `setenv()` from the start.