about summary refs log tree commit diff
path: root/src/libcore
diff options
context:
space:
mode:
authorArno Haase <arno.haase@haase-consulting.com>2019-09-10 14:04:52 +0200
committerArno Haase <arno.haase@haase-consulting.com>2019-09-10 14:04:52 +0200
commit66e4b3447110bb06930f4a606e5a47c55ca73a8a (patch)
tree105c842b3ef9be53c0a4d32b1b521dbf3ad97507 /src/libcore
parent356b4c81a04d1db70621949b25c0cc80d5c94b8e (diff)
downloadrust-66e4b3447110bb06930f4a606e5a47c55ca73a8a.tar.gz
rust-66e4b3447110bb06930f4a606e5a47c55ca73a8a.zip
typo fix
Diffstat (limited to 'src/libcore')
-rw-r--r--src/libcore/hint.rs2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/libcore/hint.rs b/src/libcore/hint.rs
index 9a581d90cc2..861ad6b5420 100644
--- a/src/libcore/hint.rs
+++ b/src/libcore/hint.rs
@@ -64,7 +64,7 @@ pub unsafe fn unreachable_unchecked() -> ! {
 /// scheduler, no overhead for switching threads occurs. However, if the thread holding the
 /// contended lock is running on the same CPU or core, the spin-loop is likely to occupy an entire CPU slice
 /// before switching to the thread that holds the lock. If the contending lock is held by a thread
-/// on the same CPU or thread or if the waiting times for acquiring the lock are longer, it is often better to
+/// on the same CPU or core or if the waiting times for acquiring the lock are longer, it is often better to
 /// use [`std::thread::yield_now`].
 ///
 /// **Note**: On platforms that do not support receiving spin-loop hints this function does not