From c46d9f6c89fc50dd80fb502677bc8d04e8260ed3 Mon Sep 17 00:00:00 2001 From: Dylan DPC <99973273+Dylan-DPC@users.noreply.github.com> Date: Wed, 23 Feb 2022 23:18:42 +0100 Subject: [PATCH] Update library/std/src/io/error.rs Co-authored-by: Josh Triplett --- library/std/src/io/error.rs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/library/std/src/io/error.rs b/library/std/src/io/error.rs index 6adf26a35a2..3df3749d676 100644 --- a/library/std/src/io/error.rs +++ b/library/std/src/io/error.rs @@ -148,7 +148,7 @@ struct Custom { /// "all other errors". /// /// In comprehensive and thorough tests that want to verify that a test doesn't return any known incorrect error kind, -/// you may want to cut-and-paste the current list of errors from here into your test code. This seems counterintuitive, +/// you may want to cut-and-paste the current full list of errors from here into your test code, and then match `_` as the correct case. This seems counterintuitive, /// but it will make your tests more robust. In particular, if you want to verify that your code does produce an /// unrecognized error kind, the robust solution is to check for all the recognized error kinds and fail in those cases. #[derive(Clone, Copy, Debug, Eq, Hash, Ord, PartialEq, PartialOrd)]