diff options
| author | Alex Crichton <alex@alexcrichton.com> | 2015-07-30 14:32:02 -0700 |
|---|---|---|
| committer | Alex Crichton <alex@alexcrichton.com> | 2015-07-30 14:32:02 -0700 |
| commit | 127e63c63b76a153a5f9afc476cfb78e390e4a3f (patch) | |
| tree | 9f05455557ab27f7e1d5e14c2de3e33436180e2b | |
| parent | 6edc994021a6bb1922ef77f62841f01a7bdf235d (diff) | |
| download | rust-127e63c63b76a153a5f9afc476cfb78e390e4a3f.tar.gz rust-127e63c63b76a153a5f9afc476cfb78e390e4a3f.zip | |
tarpl: Change norun to no_run
Needs the underscore for rustdoc to not actually run it.
| -rw-r--r-- | src/doc/tarpl/races.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/src/doc/tarpl/races.md b/src/doc/tarpl/races.md index 2ad62c14a80..21a67f11c21 100644 --- a/src/doc/tarpl/races.md +++ b/src/doc/tarpl/races.md @@ -25,7 +25,7 @@ race condition can't violate memory safety in a Rust program on its own. Only in conjunction with some other unsafe code can a race condition actually violate memory safety. For instance: -```rust,norun +```rust,no_run use std::thread; use std::sync::atomic::{AtomicUsize, Ordering}; use std::sync::Arc; @@ -56,7 +56,7 @@ thread::spawn(move || { println!("{}", data[idx.load(Ordering::SeqCst)]); ``` -```rust,norun +```rust,no_run use std::thread; use std::sync::atomic::{AtomicUsize, Ordering}; use std::sync::Arc; |
