From 010cbd011a644512afdca2378c5788181703cac3 Mon Sep 17 00:00:00 2001 From: Steve Klabnik Date: Thu, 4 Dec 2014 11:43:22 -0500 Subject: [PATCH] Tasks aren't actually lightweight :frown: Fixes #19402. --- src/doc/guide.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/src/doc/guide.md b/src/doc/guide.md index c2d43a20ec4..0280fb9e97c 100644 --- a/src/doc/guide.md +++ b/src/doc/guide.md @@ -5174,12 +5174,12 @@ processor. Rust's semantics lend themselves very nicely to solving a number of issues that programmers have with concurrency. Many concurrency errors that are runtime errors in other languages are compile-time errors in Rust. -Rust's concurrency primitive is called a **task**. Tasks are lightweight, and -do not share memory in an unsafe manner, preferring message passing to -communicate. It's worth noting that tasks are implemented as a library, and -not part of the language. This means that in the future, other concurrency -libraries can be written for Rust to help in specific scenarios. Here's an -example of creating a task: +Rust's concurrency primitive is called a **task**. Tasks are similar to +threads, and do not share memory in an unsafe manner, preferring message +passing to communicate. It's worth noting that tasks are implemented as a +library, and not part of the language. This means that in the future, other +concurrency libraries can be written for Rust to help in specific scenarios. +Here's an example of creating a task: ```{rust} spawn(proc() {