From: Manish Goregaokar Date: Sat, 1 Aug 2015 07:01:23 +0000 (+0530) Subject: Rollup merge of #27419 - cpjreynolds:master, r=Gankro X-Git-Url: https://git.lizzy.rs/?a=commitdiff_plain;h=ae9abdf705f457edc1cd0a4a01e089dbfed0007d;p=rust.git Rollup merge of #27419 - cpjreynolds:master, r=Gankro Corrects formatting of bullet-ed sentences and changes 'pervasive use raw pointers' to 'pervasive use of raw pointers'. --- ae9abdf705f457edc1cd0a4a01e089dbfed0007d diff --cc src/doc/tarpl/send-and-sync.md index af8fb43f2e9,e65dbb9b131..334d5c9dd55 --- a/src/doc/tarpl/send-and-sync.md +++ b/src/doc/tarpl/send-and-sync.md @@@ -5,13 -5,13 +5,13 @@@ multiply alias a location in memory whi synchronization to manage this access, they are absolutely not thread safe. Rust captures this with through the `Send` and `Sync` traits. - * A type is Send if it is safe to send it to another thread. A type is Sync if - * it is safe to share between threads (`&T` is Send). + * A type is Send if it is safe to send it to another thread. + * A type is Sync if it is safe to share between threads (`&T` is Send). -Send and Sync are *very* fundamental to Rust's concurrency story. As such, a +Send and Sync are fundamental to Rust's concurrency story. As such, a substantial amount of special tooling exists to make them work right. First and -foremost, they're *unsafe traits*. This means that they are unsafe *to -implement*, and other unsafe code can *trust* that they are correctly +foremost, they're [unsafe traits][]. This means that they are unsafe to +implement, and other unsafe code can that they are correctly implemented. Since they're *marker traits* (they have no associated items like methods), correctly implemented simply means that they have the intrinsic properties an implementor should have. Incorrectly implementing Send or Sync can