From 555589ef7fda4dae1ee99e5f624f88d6855773a3 Mon Sep 17 00:00:00 2001 From: Steven Fackler Date: Sun, 15 Sep 2013 23:33:00 -0700 Subject: [PATCH] Remove references to std::pipes from task tutorial This module was removed a while ago, but the tasks tutorial wasn't updated, and the old docs page for pipes was never deleted so the link confusingly still worked! --- doc/tutorial-tasks.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/doc/tutorial-tasks.md b/doc/tutorial-tasks.md index 18f35cf39a8..aa63a0112d0 100644 --- a/doc/tutorial-tasks.md +++ b/doc/tutorial-tasks.md @@ -47,8 +47,7 @@ concurrency at this writing: * [`std::task`] - All code relating to tasks and task scheduling, * [`std::comm`] - The message passing interface, -* [`std::pipes`] - The underlying messaging infrastructure, -* [`extra::comm`] - Additional messaging types based on `std::pipes`, +* [`extra::comm`] - Additional messaging types based on `std::comm`, * [`extra::sync`] - More exotic synchronization tools, including locks, * [`extra::arc`] - The Arc (atomically reference counted) type, for safely sharing immutable data, @@ -56,7 +55,6 @@ concurrency at this writing: [`std::task`]: std/task.html [`std::comm`]: std/comm.html -[`std::pipes`]: std/pipes.html [`extra::comm`]: extra/comm.html [`extra::sync`]: extra/sync.html [`extra::arc`]: extra/arc.html @@ -125,7 +123,7 @@ receiving messages. Pipes are low-level communication building-blocks and so come in a variety of forms, each one appropriate for a different use case. In what follows, we cover the most commonly used varieties. -The simplest way to create a pipe is to use the `pipes::stream` +The simplest way to create a pipe is to use the `comm::stream` function to create a `(Port, Chan)` pair. In Rust parlance, a *channel* is a sending endpoint of a pipe, and a *port* is the receiving endpoint. Consider the following example of calculating two results