Skip to content

Commit a056aea

Browse files
committed
tutorial: Minor editing
1 parent 3403e41 commit a056aea

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

doc/tutorial.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1428,10 +1428,10 @@ also done with square brackets (zero-based):
14281428
# enum crayon { almond, antique_brass, apricot,
14291429
# aquamarine, asparagus, atomic_tangerine,
14301430
# banana_mania, beaver, bittersweet };
1431-
# fn draw_crying_puppy(c: crayon) { }
1431+
# fn draw_scene(c: crayon) { }
14321432
14331433
let crayons = ~[banana_mania, beaver, bittersweet];
1434-
if crayons[0] == bittersweet { draw_crying_puppy(crayons[0]); }
1434+
if crayons[0] == bittersweet { draw_scene(crayons[0]); }
14351435
~~~~
14361436
14371437
By default, vectors are immutable—you can not replace their elements.
@@ -1644,8 +1644,8 @@ fn mk_appender(suffix: str) -> fn@(str) -> str {
16441644
16451645
## Unique closures
16461646
1647-
Unique closures, written `fn~` in analogy to the `~` pointer type (see
1648-
next section), hold on to things that can safely be sent between
1647+
Unique closures, written `fn~` in analogy to the `~` pointer type,
1648+
hold on to things that can safely be sent between
16491649
processes. They copy the values they close over, much like boxed
16501650
closures, but they also 'own' them—meaning no other code can access
16511651
them. Unique closures are used in concurrent code, particularly

0 commit comments

Comments
 (0)