about summary refs log tree commit diff
diff options
context:
space:
mode:
authorChristian Weinz <christian@madez.de>2015-06-30 17:02:10 -0300
committerChristian Weinz <christian@madez.de>2015-06-30 17:02:10 -0300
commite727dd58116e9d493163d9839f20837aff10e6ba (patch)
treeab1d521c8a2d332273972cfcca816feebf60d3a7
parent85361528bc8f3880a2b2cffd15023c20bfe98282 (diff)
downloadrust-e727dd58116e9d493163d9839f20837aff10e6ba.tar.gz
rust-e727dd58116e9d493163d9839f20837aff10e6ba.zip
Update complement-design-faq.md
The ‘_‘ wildcard handles exactly not specific cases but all nut specified.
-rw-r--r--src/doc/complement-design-faq.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/doc/complement-design-faq.md b/src/doc/complement-design-faq.md
index e887ed0cc52..5e99876f5da 100644
--- a/src/doc/complement-design-faq.md
+++ b/src/doc/complement-design-faq.md
@@ -99,7 +99,7 @@ Second, it makes cost explicit. In general, the only safe way to have a
 non-exhaustive match would be to panic the thread if nothing is matched, though
 it could fall through if the type of the `match` expression is `()`. This sort
 of hidden cost and special casing is against the language's philosophy. It's
-easy to ignore certain cases by using the `_` wildcard:
+easy to ignore all unspecified cases by using the `_` wildcard:
 
 ```rust,ignore
 match val.do_something() {