From e727dd58116e9d493163d9839f20837aff10e6ba Mon Sep 17 00:00:00 2001 From: Christian Weinz Date: Tue, 30 Jun 2015 17:02:10 -0300 Subject: [PATCH] Update complement-design-faq.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The ‘_‘ wildcard handles exactly not specific cases but all nut specified. --- src/doc/complement-design-faq.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/doc/complement-design-faq.md b/src/doc/complement-design-faq.md index e887ed0cc5297..5e99876f5dab8 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() {