about summary refs log tree commit diff
diff options
context:
space:
mode:
authorBrody Holden <brody.holden.r@gmail.com>2015-06-24 20:08:55 -0700
committerBrody Holden <brody.holden.r@gmail.com>2015-06-24 20:08:55 -0700
commit165a2817a413fd08eb7feeae145554d219f20552 (patch)
tree9684c934874c88b0e3c5980abf1e4b5b4640ad06
parenta6430925b435d5c27bb7fb4088dee06817c83d87 (diff)
downloadrust-165a2817a413fd08eb7feeae145554d219f20552.tar.gz
rust-165a2817a413fd08eb7feeae145554d219f20552.zip
Replace std::comm reference with std::sync::mpsc.
The FFI documentation references std::comm. Replace with
std::sync::mpsc.

Also wrap the line.
-rw-r--r--src/doc/trpl/ffi.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/doc/trpl/ffi.md b/src/doc/trpl/ffi.md
index 917d8dbe196..442a1f062ef 100644
--- a/src/doc/trpl/ffi.md
+++ b/src/doc/trpl/ffi.md
@@ -309,8 +309,8 @@ and invokes callbacks from there.
 In these cases access to Rust data structures inside the callbacks is
 especially unsafe and proper synchronization mechanisms must be used.
 Besides classical synchronization mechanisms like mutexes, one possibility in
-Rust is to use channels (in `std::comm`) to forward data from the C thread
-that invoked the callback into a Rust thread.
+Rust is to use channels (in `std::sync::mpsc`) to forward data from the C
+thread that invoked the callback into a Rust thread.
 
 If an asynchronous callback targets a special object in the Rust address space
 it is also absolutely necessary that no more callbacks are performed by the