From 057dc09eaea610c5a14d0908764696d9d416d544 Mon Sep 17 00:00:00 2001 From: Dylan DPC Date: Wed, 23 Feb 2022 03:29:02 +0100 Subject: [PATCH] add some more summary from pr discussion --- 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 e4961952d0b..6adf26a35a2 100644 --- a/library/std/src/io/error.rs +++ b/library/std/src/io/error.rs @@ -147,7 +147,7 @@ struct Custom { /// In application code, use `match` for the `ErrorKind` values you are expecting; use `_` to match /// "all other errors". /// -/// In comprehensive and thorough tests that want to verify that a test doesn't return any known incorrect error kind, +/// 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, /// 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.