Merge pull request scala#198 from xeno-by/master

xeno-by · xeno-by · commit e8e629119974 · 2013-05-19T04:36:25.000-07:00
oops forgot to link to an example
diff --git a/overviews/macros/untypedmacros.md b/overviews/macros/untypedmacros.md
@@ -51,7 +51,9 @@ The former will lead to a compile error, the latter, as in e.g. `List[_]`, will
 
 Note that untyped macros enable extractor macros: [SI-5903](https://issues.scala-lang.org/browse/SI-5903). In 2.10.x, it is possible
 to declare `unapply` or `unapplySeq` as macros, but usability of such macros is extremely limited as described in the discussion
-of the linked JIRA issue. Untyped macros make the full power of textual abstraction available in pattern matching.
+of the linked JIRA issue. Untyped macros make the full power of textual abstraction available in pattern matching. The
+[test/files/run/macro-expand-unapply-c](https://github.com/scalamacros/kepler/tree/paradise/macros/test/files/run/macro-expand-unapply-c)
+unit test provides details on this matter.
 
 If a macro has one or more untyped parameters, then when typing its expansions, the typechecker will do nothing to its arguments
 and will pass them to the macro untyped. Even if some of the parameters do have type annotations, they will currently be ignored. This
