From 4b19be36319d6a0398b36a1d529d3defe30e31a2 Mon Sep 17 00:00:00 2001 From: Steve Klabnik Date: Tue, 7 Jul 2015 09:29:04 -0400 Subject: [PATCH] Not literally all of concurrency is a library Fixes #26344 --- src/doc/trpl/concurrency.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/src/doc/trpl/concurrency.md b/src/doc/trpl/concurrency.md index ccd769089d251..15c19ece48a14 100644 --- a/src/doc/trpl/concurrency.md +++ b/src/doc/trpl/concurrency.md @@ -10,11 +10,12 @@ 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 -to understand something: Rust is low-level enough that all of this is provided -by the standard library, not by the language. This means that if you don't like -some aspect of the way Rust handles concurrency, you can implement an alternative -way of doing things. [mio](https://github.com/carllerche/mio) is a real-world -example of this principle in action. +to understand something: Rust is low-level enough that the vast majority of +this is provided by the standard library, not by the language. This means that +if you don't like some aspect of the way Rust handles concurrency, you can +implement an alternative way of doing things. +[mio](https://github.com/carllerche/mio) is a real-world example of this +principle in action. ## Background: `Send` and `Sync`