---

yaml
---
r: 37871
b: refs/heads/try
c: b4501f4
h: refs/heads/master
i:
  37869: d47c39a
  37867: b91ea43
  37863: 2552b90
  37855: 55370bb
v: v3

Author: catamorphism

[refs]

@@ -2,7 +2,7 @@
 refs/heads/master: 09bb07bed9166105ea961a42b5fff7739ae0d2e9
 refs/heads/snap-stage1: e33de59e47c5076a89eadeb38f4934f58a3618a6
 refs/heads/snap-stage3: eb8fd119c65c67f3b1b8268cc7341c22d39b7b61
-refs/heads/try: 31a4f40329bec3507ed014700c7d91b1697875e3
+refs/heads/try: b4501f4c64501a8ac738288665a0499ecb0aa9b8
 refs/tags/release-0.1: 1f5c5126e96c79d22cb7862f75304136e204f105
 refs/heads/ndm: f3868061cd7988080c30d6d5bf352a5a5fe2460b
 refs/heads/try2: a810c03263670238bccd64cabb12a23a46e3a278

branches/try/doc/rust.md

@@ -2244,8 +2244,9 @@ The compiler interprets a variable pattern `x` as a binding _only_ if there is n
 A convention you can use to avoid conflicts is simply to name variants with upper-case letters,
 and local variables with lower-case letters.
 
-Multiple match patterns may be joined with the `|` operator.  A
-range of values may be specified with `..`. For example:
+Multiple match patterns may be joined with the `|` operator.
+A range of values may be specified with `..`.
+For example:
 
 ~~~~
 # let x = 2;
@@ -2257,6 +2258,10 @@ let message = match x {
 };
 ~~~~
 
+Range patterns only work on scalar types
+(like integers and characters; not like vectors and structs, which have sub-components).
+A range pattern may not be a sub-range of another range pattern inside the same `match`.
+
 Finally, match patterns can accept *pattern guards* to further refine the
 criteria for matching a case. Pattern guards appear after the pattern and
 consist of a bool-typed expression following the `if` keyword. A pattern