@@ -2526,7 +2526,7 @@ The currently implemented features of the reference compiler are:
2526
2526
2527
2527
* ` plugin_registrar ` - Indicates that a crate has [ compiler plugins] [ plugin ] that it
2528
2528
wants to load. As with ` phase ` , the implementation is
2529
- in need of a overhaul, and it is not clear that plugins
2529
+ in need of an overhaul, and it is not clear that plugins
2530
2530
defined using this will continue to work.
2531
2531
2532
2532
* ` quote ` - Allows use of the ` quote_*! ` family of macros, which are
@@ -2583,7 +2583,7 @@ there isn't a parser error first). The directive in this case is no longer
2583
2583
necessary, and it's likely that existing code will break if the feature isn't
2584
2584
removed.
2585
2585
2586
- If a unknown feature is found in a directive, it results in a compiler error.
2586
+ If an unknown feature is found in a directive, it results in a compiler error.
2587
2587
An unknown feature is one which has never been recognized by the compiler.
2588
2588
2589
2589
# Statements and expressions
@@ -2685,7 +2685,7 @@ When an lvalue is evaluated in an _lvalue context_, it denotes a memory
2685
2685
location; when evaluated in an _ rvalue context_ , it denotes the value held _ in_
2686
2686
that memory location.
2687
2687
2688
- When an rvalue is used in lvalue context, a temporary un-named lvalue is
2688
+ When an rvalue is used in an lvalue context, a temporary un-named lvalue is
2689
2689
created and used instead. A temporary's lifetime equals the largest lifetime
2690
2690
of any reference that points to it.
2691
2691
@@ -2833,7 +2833,7 @@ foo().x;
2833
2833
```
2834
2834
2835
2835
A field access is an [ lvalue] ( #lvalues,-rvalues-and-temporaries ) referring to
2836
- the value of that field. When the type providing the field inherits mutabilty ,
2836
+ the value of that field. When the type providing the field inherits mutability ,
2837
2837
it can be [ assigned] ( #assignment-expressions ) to.
2838
2838
2839
2839
Also, if the type of the expression to the left of the dot is a pointer, it is
@@ -3108,11 +3108,10 @@ then the expression completes.
3108
3108
Some examples of call expressions:
3109
3109
3110
3110
```
3111
- # use std::from_str::FromStr;
3112
3111
# fn add(x: int, y: int) -> int { 0 }
3113
3112
3114
3113
let x: int = add(1, 2);
3115
- let pi: Option<f32> = FromStr:: from_str("3.14");
3114
+ let pi: Option<f32> = from_str("3.14");
3116
3115
```
3117
3116
3118
3117
### Lambda expressions
@@ -3321,7 +3320,7 @@ between `_` and `..` is that the pattern `C(_)` is only type-correct if `C` has
3321
3320
exactly one argument, while the pattern ` C(..) ` is type-correct for any enum
3322
3321
variant ` C ` , regardless of how many arguments ` C ` has.
3323
3322
3324
- Used inside a array pattern, ` .. ` stands for any number of elements, when the
3323
+ Used inside an array pattern, ` .. ` stands for any number of elements, when the
3325
3324
` advanced_slice_patterns ` feature gate is turned on. This wildcard can be used
3326
3325
at most once for a given array, which implies that it cannot be used to
3327
3326
specifically match elements that are at an unknown distance from both ends of a
@@ -3584,7 +3583,7 @@ is not a surrogate), represented as a 32-bit unsigned word in the 0x0000 to
3584
3583
0xD7FF or 0xE000 to 0x10FFFF range. A ` [char] ` array is effectively an UCS-4 /
3585
3584
UTF-32 string.
3586
3585
3587
- A value of type ` str ` is a Unicode string, represented as a array of 8-bit
3586
+ A value of type ` str ` is a Unicode string, represented as an array of 8-bit
3588
3587
unsigned bytes holding a sequence of UTF-8 codepoints. Since ` str ` is of
3589
3588
unknown size, it is not a _ first class_ type, but can only be instantiated
3590
3589
through a pointer type, such as ` &str ` or ` String ` .
0 commit comments