---

yaml
---
r: 28006
b: refs/heads/try
c: 0698fc6
h: refs/heads/master
v: v3

Author: paulstansifer

[refs]

@@ -2,7 +2,7 @@
 refs/heads/master: cd6f24f9d14ac90d167386a56e7a6ac1f0318195
 refs/heads/snap-stage1: e33de59e47c5076a89eadeb38f4934f58a3618a6
 refs/heads/snap-stage3: cd6f24f9d14ac90d167386a56e7a6ac1f0318195
-refs/heads/try: e9622f09aa0d8c70022f4bf3ea516d7349c2990c
+refs/heads/try: 0698fc665033f905470a4b98ea82bdb4f8342352
 refs/tags/release-0.1: 1f5c5126e96c79d22cb7862f75304136e204f105
 refs/heads/ndm: f3868061cd7988080c30d6d5bf352a5a5fe2460b
 refs/heads/try2: d0c6ce338884ee21843f4b40bf6bf18d222ce5df

branches/try/doc/tutorial.md

@@ -2411,6 +2411,11 @@ The right-hand side of the `=>` follows the same rules as the left-hand side,
 except that `$` need only be followed by the name of the syntactic fragment
 to transcribe.
 
+The right-hand side must be surrounded by delimiters of some kind, and must be
+an expression; currently, user-defined macros can only be invoked in
+expression position (even though `macro_rules!` itself can be in item
+position).
+
 ## Multiplicity
 
 ### Invocation