about summary refs log tree commit diff
path: root/src/doc
diff options
context:
space:
mode:
authorDoug Goldstein <cardoe@cardoe.com>2016-08-07 10:14:01 -0500
committerDoug Goldstein <cardoe@cardoe.com>2016-08-08 11:10:44 -0500
commit18565c63db1982b927b291b9597368efc615d91c (patch)
tree90a79473fdb411a0d317b3a49df80d694a5f3fe1 /src/doc
parent42903d9a8f0f471f5e0eb453e49fe44a65a746c5 (diff)
downloadrust-18565c63db1982b927b291b9597368efc615d91c.tar.gz
rust-18565c63db1982b927b291b9597368efc615d91c.zip
book: update example patterns to be more clear
When using Point { x: 0, y: 0 } and showing pattern matching decomposing
x and y individually its hard to understand. By using a different value
for x and a different value for y it is more clear.
Diffstat (limited to 'src/doc')
-rw-r--r--src/doc/book/patterns.md12
1 files changed, 6 insertions, 6 deletions
diff --git a/src/doc/book/patterns.md b/src/doc/book/patterns.md
index a0245d4c7b1..910b1375476 100644
--- a/src/doc/book/patterns.md
+++ b/src/doc/book/patterns.md
@@ -109,14 +109,14 @@ struct Point {
     y: i32,
 }
 
-let origin = Point { x: 0, y: 0 };
+let point = Point { x: 2, y: 3 };
 
-match origin {
+match point {
     Point { x, .. } => println!("x is {}", x),
 }
 ```
 
-This prints `x is 0`.
+This prints `x is 2`.
 
 You can do this kind of match on any member, not only the first:
 
@@ -126,14 +126,14 @@ struct Point {
     y: i32,
 }
 
-let origin = Point { x: 0, y: 0 };
+let point = Point { x: 2, y: 3 };
 
-match origin {
+match point {
     Point { y, .. } => println!("y is {}", y),
 }
 ```
 
-This prints `y is 0`.
+This prints `y is 3`.
 
 This ‘destructuring’ behavior works on any compound data type, like
 [tuples][tuples] or [enums][enums].