From 4f7a3784a5d224bc4cbc9bd1a4418facc301726f Mon Sep 17 00:00:00 2001 From: Nadrieril Date: Sat, 9 May 2020 19:00:37 +0100 Subject: [PATCH] typo --- src/librustc_mir_build/hair/pattern/_match.rs | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/src/librustc_mir_build/hair/pattern/_match.rs b/src/librustc_mir_build/hair/pattern/_match.rs index f94da2f3805a..7964bd29e78c 100644 --- a/src/librustc_mir_build/hair/pattern/_match.rs +++ b/src/librustc_mir_build/hair/pattern/_match.rs @@ -963,11 +963,12 @@ impl<'p, 'tcx> FilteredField<'p, 'tcx> { /// /// If a private or `non_exhaustive` field is uninhabited, the code mustn't observe that it is /// uninhabited. For that, we filter these fields out of the matrix. This is subtle because we -/// still need to have those fields back when going to/from a `Pat`. Mot of this is handled -/// automatically in `Fields`, but when constructing or deconstructing fields you need to use the -/// correct method. As a rule, when going to/from the matrix, use the filtered field list; when -/// going to/from `Pat`, use the full field list. -/// This filtering is uncommon in practice, because uninhabited fields are rarely used. +/// still need to have those fields back when going to/from a `Pat`. Most of this is handled +/// automatically in `Fields`, but when constructing or deconstructing `Fields` you need to be +/// careful. As a rule, when going to/from the matrix, use the filtered field list; when going +/// to/from `Pat`, use the full field list. +/// This filtering is uncommon in practice, because uninhabited fields are rarely used, so we avoid +/// it when possible to preserve performance. #[derive(Debug, Clone)] enum Fields<'p, 'tcx> { /// Lists of patterns that don't contain any filtered fields.