summary refs log tree commit diff
path: root/src/doc/tutorial.md
diff options
context:
space:
mode:
authorchromatic <chromatic@wgz.org>2014-02-04 16:06:41 -0800
committerchromatic <chromatic@wgz.org>2014-02-04 16:11:32 -0800
commit87d026b76e9f389497aa48b23755d88a18127757 (patch)
tree730641dd98f31632e3cb3ec7a6f7e6d201d0b5cc /src/doc/tutorial.md
parentacb1ec0b6715a529e3f6a7053737d99f03971c27 (diff)
downloadrust-87d026b76e9f389497aa48b23755d88a18127757.tar.gz
rust-87d026b76e9f389497aa48b23755d88a18127757.zip
Improved pattern-match code and explanation.
This cleans up a warning about an unused variable and explains the code
further.
Diffstat (limited to 'src/doc/tutorial.md')
-rw-r--r--src/doc/tutorial.md6
1 files changed, 4 insertions, 2 deletions
diff --git a/src/doc/tutorial.md b/src/doc/tutorial.md
index a7696b45405..75a5840a1ef 100644
--- a/src/doc/tutorial.md
+++ b/src/doc/tutorial.md
@@ -509,7 +509,7 @@ fn angle(vector: (f64, f64)) -> f64 {
     let pi = f64::consts::PI;
     match vector {
       (0.0, y) if y < 0.0 => 1.5 * pi,
-      (0.0, y) => 0.5 * pi,
+      (0.0, _) => 0.5 * pi,
       (x, y) => atan(y / x)
     }
 }
@@ -519,7 +519,9 @@ A variable name in a pattern matches any value, *and* binds that name
 to the value of the matched value inside of the arm's action. Thus, `(0.0,
 y)` matches any tuple whose first element is zero, and binds `y` to
 the second element. `(x, y)` matches any two-element tuple, and binds both
-elements to variables.
+elements to variables. `(0.0,_)` matches any tuple whose first element is zero
+and does not bind anything to the second element.
+
 A subpattern can also be bound to a variable, using `variable @ pattern`. For
 example: