diff options
| author | David Reid <dreid@dreid.org> | 2015-05-14 08:15:50 -0700 |
|---|---|---|
| committer | David Reid <dreid@dreid.org> | 2015-05-14 08:15:50 -0700 |
| commit | acb5e02add66093eef3f47ca5a5bce22ceac7684 (patch) | |
| tree | 43bc3eb06ee9cb759a843e636742191880bec547 | |
| parent | b1bd3a3c5180b2d671e5810cb5211b2d2b456a71 (diff) | |
| download | rust-acb5e02add66093eef3f47ca5a5bce22ceac7684.tar.gz rust-acb5e02add66093eef3f47ca5a5bce22ceac7684.zip | |
Another thread->task fix.
| -rw-r--r-- | src/doc/trpl/concurrency.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/doc/trpl/concurrency.md b/src/doc/trpl/concurrency.md index d6590e956a8..3c64e0b14de 100644 --- a/src/doc/trpl/concurrency.md +++ b/src/doc/trpl/concurrency.md @@ -6,7 +6,7 @@ and more cores, yet many programmers aren't prepared to fully utilize them. Rust's memory safety features also apply to its concurrency story too. Even concurrent Rust programs must be memory safe, having no data races. Rust's type -system is up to the thread, and gives you powerful ways to reason about +system is up to the task, and gives you powerful ways to reason about concurrent code at compile time. Before we talk about the concurrency features that come with Rust, it's important |