@@ -1428,10 +1428,10 @@ also done with square brackets (zero-based):
1428
1428
# enum crayon { almond, antique_brass, apricot,
1429
1429
# aquamarine, asparagus, atomic_tangerine,
1430
1430
# banana_mania, beaver, bittersweet };
1431
- # fn draw_crying_puppy (c: crayon) { }
1431
+ # fn draw_scene (c: crayon) { }
1432
1432
1433
1433
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]); }
1435
1435
~~~~
1436
1436
1437
1437
By default, vectors are immutable—you can not replace their elements.
@@ -1644,8 +1644,8 @@ fn mk_appender(suffix: str) -> fn@(str) -> str {
1644
1644
1645
1645
## Unique closures
1646
1646
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
1649
1649
processes. They copy the values they close over, much like boxed
1650
1650
closures, but they also 'own' them—meaning no other code can access
1651
1651
them. Unique closures are used in concurrent code, particularly
0 commit comments