From 29b04a269a96e22353728f56ba33b3e331bb1f61 Mon Sep 17 00:00:00 2001 From: Matthias Beyer Date: Fri, 26 Apr 2019 16:15:34 +0200 Subject: [PATCH] doc: Rewrite section on error handling in libraries Signed-off-by: Matthias Beyer --- doc/src/03010-conventions.md | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/doc/src/03010-conventions.md b/doc/src/03010-conventions.md index ccee1323..5e9ffe7e 100644 --- a/doc/src/03010-conventions.md +++ b/doc/src/03010-conventions.md @@ -63,12 +63,8 @@ think hard whether this is really necessary. ### Library error types/kinds -Libraries must use "error-chain" to create error types and kinds. -Most likely, a library needs some kinds for wrapping the errors from underlying -libraries, such as the store itself. +Libraries must use "failure" to create error objects. -A library must _never_ introduce multiple error types, but is free to introduce -as many error kinds as required. ### Libraries with commandline frontends