---

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

Author: catamorphism

[refs]

@@ -6,7 +6,7 @@ refs/heads/try: d324a424d8f84b1eb049b12cf34182bda91b0024
 refs/tags/release-0.1: 1f5c5126e96c79d22cb7862f75304136e204f105
 refs/heads/ndm: f3868061cd7988080c30d6d5bf352a5a5fe2460b
 refs/heads/try2: d0c6ce338884ee21843f4b40bf6bf18d222ce5df
-refs/heads/incoming: 5e22fb9c7f94c76e1e7e17709884198ec4ba3fcb
+refs/heads/incoming: 00d71087e5caeacf264f4b57b198be32afda6914
 refs/heads/dist-snap: 2f32a1581f522e524009138b33b1c7049ced668d
 refs/tags/release-0.2: c870d2dffb391e14efb05aa27898f1f6333a9596
 refs/tags/release-0.3: b5f0d0f648d9a6153664837026ba1be43d3e2503

branches/incoming/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.