add some more summary from pr discussion
This commit is contained in:
parent
37cbc7d120
commit
057dc09eae
@ -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.
|
||||
|
Loading…
x
Reference in New Issue
Block a user