diff options
| author | Colin Walters <walters@verbum.org> | 2015-04-23 16:59:36 -0400 |
|---|---|---|
| committer | Colin Walters <walters@verbum.org> | 2015-05-13 21:14:15 -0400 |
| commit | 44a5bf1b7d8d16e73ab5631c4dd6bd5107079c5f (patch) | |
| tree | 83a63e9df086dbaa72f906b6d54999e4f0b44449 /src/libstd/array.rs | |
| parent | 222cd73b8a422d2c4124375f6aaffd2663bb9718 (diff) | |
| download | rust-44a5bf1b7d8d16e73ab5631c4dd6bd5107079c5f.tar.gz rust-44a5bf1b7d8d16e73ab5631c4dd6bd5107079c5f.zip | |
libstd/env: Add non-Rust synchronization warnings for setenv()
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. It looks like Rust has an internal mutex, which helps for apps that are pure Rust, but it will be an evil trap for someone later adding in native code (apps like Servo and games will be at risk). Java got this right by disallowing `setenv()` from the start. I suggest Rust program authors only use `setenv()` early in main.
Diffstat (limited to 'src/libstd/array.rs')
0 files changed, 0 insertions, 0 deletions