about summary refs log tree commit diff
path: root/src/libstd/sync
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2015-03-23 00:37:35 +0000
committerbors <bors@rust-lang.org>2015-03-23 00:37:35 +0000
commit809a554fca2d0ebc2ba50077016fe282a4064752 (patch)
treeeb7494e5b785d5abb724393c4ade43ed572f9c89 /src/libstd/sync
parentb0aad7dd4fad8d7e2e2f877a511a637258949597 (diff)
parentb4e9106a8a476c2b77e2c4cd8717a9bc1b95de52 (diff)
downloadrust-809a554fca2d0ebc2ba50077016fe282a4064752.tar.gz
rust-809a554fca2d0ebc2ba50077016fe282a4064752.zip
Auto merge of #23593 - Manishearth:rollup, r=Manishearth
(yay, no Saturday)
Diffstat (limited to 'src/libstd/sync')
-rw-r--r--src/libstd/sync/mutex.rs4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/libstd/sync/mutex.rs b/src/libstd/sync/mutex.rs
index 1cbfbbf2927..130fd1d7dc8 100644
--- a/src/libstd/sync/mutex.rs
+++ b/src/libstd/sync/mutex.rs
@@ -40,7 +40,7 @@ use fmt;
 /// among threads to ensure that a possibly invalid invariant is not witnessed.
 ///
 /// A poisoned mutex, however, does not prevent all access to the underlying
-/// data. The `PoisonError` type has an `into_guard` method which will return
+/// data. The `PoisonError` type has an `into_inner` method which will return
 /// the guard that would have otherwise been returned on a successful lock. This
 /// allows access to the data, despite the lock being poisoned.
 ///
@@ -105,7 +105,7 @@ use fmt;
 /// // pattern matched on to return the underlying guard on both branches.
 /// let mut guard = match lock.lock() {
 ///     Ok(guard) => guard,
-///     Err(poisoned) => poisoned.into_guard(),
+///     Err(poisoned) => poisoned.into_inner(),
 /// };
 ///
 /// *guard += 1;