---

yaml
---
r: 24127
b: refs/heads/master
c: ba8750a
h: refs/heads/master
i:
  24125: 54483ab
  24123: d72d1ee
  24119: d2f6b04
  24111: 95bbb3a
  24095: d27837f
  24063: fff145a
v: v3

Author: brson

[refs]

@@ -1,5 +1,5 @@
 ---
-refs/heads/master: a8406e3d00ca791317f85d369e6157e4b5a2cf90
+refs/heads/master: ba8750a5503242828ca0d95177196ebe6d7cbf51
 refs/heads/snap-stage1: e33de59e47c5076a89eadeb38f4934f58a3618a6
 refs/heads/snap-stage3: cd6f24f9d14ac90d167386a56e7a6ac1f0318195
 refs/heads/try: ffbe0e0e00374358b789b0037bcb3a577cd218be

trunk/doc/tutorial.md

@@ -580,8 +580,8 @@ you use the matching to get at the contents of data types. Remember
 that `(float, float)` is a tuple of two floats:
 
 ~~~~
-use float::consts::pi;
 fn angle(vector: (float, float)) -> float {
+    let pi = float::consts::pi;
     match vector {
       (0f, y) if y < 0f => 1.5 * pi,
       (0f, y) => 0.5 * pi,
@@ -601,23 +601,19 @@ an expression of type `bool` that determines, after the pattern is
 found to match, whether the arm is taken or not. The variables bound
 by the pattern are available in this guard expression.
 
-## Let
-
-You've already seen simple `let` bindings. `let` is also a little fancier: it
-is possible to use destructuring patterns in it. For example, you can say this
-to extract the fields from a tuple:
+You've already seen simple `let` bindings, but `let` is a little
+fancier than you've been led to believe. It too supports destructuring
+patterns. For example, you can say this to extract the fields from a
+tuple, introducing two variables, `a` and `b`.
 
 ~~~~
 # fn get_tuple_of_two_ints() -> (int, int) { (1, 1) }
 let (a, b) = get_tuple_of_two_ints();
 ~~~~
 
-This will introduce two new variables, `a` and `b`, bound to the
-content of the tuple.
-
-You may only use *irrefutable* patterns—patterns that can never fail to
-match—in let bindings. Other types of patterns, such as literals, are
-not allowed.
+Let bindings only work with _irrefutable_ patterns, that is, patterns
+that can never fail to match. This excludes `let` from matching
+literals and most enum variants.
 
 ## Loops