---

yaml
---
r: 23478
b: refs/heads/master
c: 00d7108
h: refs/heads/master
v: v3

Author: catamorphism

[refs]

@@ -1,5 +1,5 @@
 ---
-refs/heads/master: 5e22fb9c7f94c76e1e7e17709884198ec4ba3fcb
+refs/heads/master: 00d71087e5caeacf264f4b57b198be32afda6914
 refs/heads/snap-stage1: e33de59e47c5076a89eadeb38f4934f58a3618a6
 refs/heads/snap-stage3: cd6f24f9d14ac90d167386a56e7a6ac1f0318195
 refs/heads/try: ffbe0e0e00374358b789b0037bcb3a577cd218be

trunk/doc/tutorial.md

@@ -751,10 +751,7 @@ match my_number {
 If the arm with the wildcard pattern was left off in the above
 example, the typechecker would reject it at compile time. `match`
 constructs must be exhaustive: they must have an arm covering every
-possible case. (You may use the `match check` construct to write a
-non-exhaustive match, but it's highly undesirable to do so. You may
-reason that the missing cases will never occur, but the typechecker
-provides you with no assurance that your reasoning is correct.)
+possible case.
 
 A powerful application of pattern matching is *destructuring*, where
 you use the matching to get at the contents of data types. Remember
@@ -850,8 +847,6 @@ task failure:
 
 * Accessing an out-of-bounds element of a vector.
 
-* Having no clauses match when evaluating an `match check` expression.
-
 * An assertion failure.
 
 * Integer division by zero.