File tree Expand file tree Collapse file tree 1 file changed +5
-5
lines changed Expand file tree Collapse file tree 1 file changed +5
-5
lines changed Original file line number Diff line number Diff line change @@ -144,13 +144,13 @@ struct Custom {
144144///
145145/// # Handling errors and matching on `ErrorKind`
146146///
147- /// In application code, use `match` for the `ErrorKind` values you are
147+ /// In application code, use `match` for the `ErrorKind` values you are
148148/// expecting; use `_` to match "all other errors".
149149///
150- /// In comprehensive and thorough tests that want to verify that a test doesn't
151- /// return any known incorrect error kind, you may want to cut-and-paste the
152- /// current full list of errors from here into your test code, and then match
153- /// `_` as the correct case. This seems counterintuitive, but it will make your
150+ /// In comprehensive and thorough tests that want to verify that a test doesn't
151+ /// return any known incorrect error kind, you may want to cut-and-paste the
152+ /// current full list of errors from here into your test code, and then match
153+ /// `_` as the correct case. This seems counterintuitive, but it will make your
154154/// tests more robust. In particular, if you want to verify that your code does
155155/// produce an unrecognized error kind, the robust solution is to check for all
156156/// the recognized error kinds and fail in those cases.
You can’t perform that action at this time.
0 commit comments