From d7e1d5f0c275c6e876f97a3d95d27a020bc88046 Mon Sep 17 00:00:00 2001 From: Nadrieril Date: Tue, 19 May 2020 17:02:31 +0100 Subject: [PATCH] Make caveat more precise --- src/librustc_mir_build/hair/pattern/_match.rs | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/src/librustc_mir_build/hair/pattern/_match.rs b/src/librustc_mir_build/hair/pattern/_match.rs index 16d783fcad213..626e531c807b7 100644 --- a/src/librustc_mir_build/hair/pattern/_match.rs +++ b/src/librustc_mir_build/hair/pattern/_match.rs @@ -65,8 +65,7 @@ /// /// Caveat: this constructors/fields distinction doesn't quite cover every Rust value. For example /// a value of type `Rc` doesn't fit this idea very well, nor do various other things. -/// However, this idea covers everything that can be pattern-matched, and this is all we need for -/// exhaustiveness checking. +/// However, this idea covers most of the cases that are relevant to exhaustiveness checking. /// /// /// # Algorithm