diff options
| author | Jacob Pratt <jacob@jhpratt.dev> | 2024-06-16 03:41:58 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-06-16 03:41:58 -0400 |
| commit | 623cf23621f816a8936c627ec8a73a933b3f956f (patch) | |
| tree | 70a387351ab64317c02391ea657f76bf5c86e41a /library/std/src | |
| parent | e345ddb2d1ee4c6df1eb63e1695cb6d804ee7fe5 (diff) | |
| parent | 893f95f1f7c663c67c884120003b3bf21b0af61a (diff) | |
| download | rust-623cf23621f816a8936c627ec8a73a933b3f956f.tar.gz rust-623cf23621f816a8936c627ec8a73a933b3f956f.zip | |
Rollup merge of #126539 - lukaslueg:patch-1, r=jhpratt
Update `Arc::try_unwrap()` docs Clarify the language wrt "race condition" not meaning "memory unsafety". The docs make an important point about a 'logical' race condition that can occur if the `Err`-case in `Arc::try_unwrap()` is not handled properly. The language as is uses the term "race condition", which the reader may associate with "memory unsafety". This PR tries to clarify the scenario and qualify "race condition without memory unsafety".
Diffstat (limited to 'library/std/src')
0 files changed, 0 insertions, 0 deletions