diff options
| author | bors <bors@rust-lang.org> | 2015-05-14 07:15:51 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2015-05-14 07:15:51 +0000 |
| commit | 0a1a53d6933b53b804269ce236760847c5dd00fa (patch) | |
| tree | 62c6473f672213d5db737ffb671291d583b3080e /src/rustllvm/ExecutionEngineWrapper.cpp | |
| parent | e77b03d783b5c9df88f1f743fe29615db43e1dda (diff) | |
| parent | 44a5bf1b7d8d16e73ab5631c4dd6bd5107079c5f (diff) | |
| download | rust-0a1a53d6933b53b804269ce236760847c5dd00fa.tar.gz rust-0a1a53d6933b53b804269ce236760847c5dd00fa.zip | |
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.
Diffstat (limited to 'src/rustllvm/ExecutionEngineWrapper.cpp')
0 files changed, 0 insertions, 0 deletions