Skip to content

Commit 75f30a2

Browse files
committed
---
yaml --- r: 134693 b: refs/heads/try c: 19e814e h: refs/heads/master i: 134691: ea53c8e v: v3
1 parent e0cc4a6 commit 75f30a2

File tree

2 files changed

+5
-5
lines changed

2 files changed

+5
-5
lines changed

[refs]

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
refs/heads/master: 58413c09cd52ea4005d6ea7733ba1fb3a8f36589
33
refs/heads/snap-stage1: e33de59e47c5076a89eadeb38f4934f58a3618a6
44
refs/heads/snap-stage3: 437179ed8bf7f7672f84b19265df1ce569e70490
5-
refs/heads/try: 96180d7e6bcb68e881664483ce3d7db91a0c72de
5+
refs/heads/try: 19e814ed9895c64ef362fe5834bc15678a8f10c3
66
refs/tags/release-0.1: 1f5c5126e96c79d22cb7862f75304136e204f105
77
refs/heads/ndm: f3868061cd7988080c30d6d5bf352a5a5fe2460b
88
refs/heads/try2: 147ecfdd8221e4a4d4e090486829a06da1e0ca3c

branches/try/src/doc/reference.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1388,7 +1388,7 @@ global data section (such as string constants and static items) can have the
13881388
`static` lifetime. Static items are declared with the `static` keyword. A
13891389
static item must have a _constant expression_ giving its definition.
13901390

1391-
Static items must be explicitly typed. The type may be ```bool```, ```char```,
1391+
Static items must be explicitly typed. The type may be `bool`, `char`,
13921392
a number, or a type derived from those primitive types. The derived types are
13931393
references with the `static` lifetime, fixed-size arrays, tuples, and structs.
13941394

@@ -1412,16 +1412,16 @@ static bits_n_strings: BitsNStrings<'static> = BitsNStrings {
14121412

14131413
#### Mutable statics
14141414

1415-
If a static item is declared with the ```mut``` keyword, then it is allowed to
1415+
If a static item is declared with the `mut` keyword, then it is allowed to
14161416
be modified by the program. One of Rust's goals is to make concurrency bugs
14171417
hard to run into, and this is obviously a very large source of race conditions
1418-
or other bugs. For this reason, an ```unsafe``` block is required when either
1418+
or other bugs. For this reason, an `unsafe` block is required when either
14191419
reading or writing a mutable static variable. Care should be taken to ensure
14201420
that modifications to a mutable static are safe with respect to other tasks
14211421
running in the same process.
14221422

14231423
Mutable statics are still very useful, however. They can be used with C
1424-
libraries and can also be bound from C libraries (in an ```extern``` block).
1424+
libraries and can also be bound from C libraries (in an `extern` block).
14251425

14261426
```
14271427
# fn atomic_add(_: &mut uint, _: uint) -> uint { 2 }

0 commit comments

Comments
 (0)