diff options
| author | Mica White <botahamec@outlook.com> | 2024-03-11 16:51:15 -0400 |
|---|---|---|
| committer | Mica White <botahamec@outlook.com> | 2024-03-11 16:51:15 -0400 |
| commit | 367ea452b09e1a0a8c67bb309073d37792bb748d (patch) | |
| tree | cb84fca081e6ae83655d56044ccfd767d5642af6 | |
| parent | 8a568aeef00cb811a732894c7b55a7c3c31b242b (diff) | |
Doc bug fix
| -rw-r--r-- | src/lib.rs | 3 |
1 files changed, 1 insertions, 2 deletions
@@ -37,7 +37,7 @@ //! [`LockCollection::new_unchecked`] doesn't do this check, but is unsafe to //! call. //! -//! **Avoid using distinct lock orders for `LockCollection`.** The problem is +//! **Avoid using distinct lock orders for [`LockCollection`].** The problem is //! that this library must iterate through the list of locks, and not complete //! until every single one of them is unlocked. This also means that attempting //! to lock multiple mutexes gives you a lower chance of ever running. Only one @@ -104,7 +104,6 @@ //! println!("{}", *data.0); //! println!("{}", *data.1); //! ``` -//! ``` mod collection; mod key; |
