mirror of
https://github.com/haraldh/chainerror.git
synced 2025-01-31 00:56:41 +01:00
Header change
This commit is contained in:
parent
fe73f84b85
commit
e0a837873a
|
@ -1,4 +1,4 @@
|
|||
## Simple String Errors
|
||||
# Simple String Errors
|
||||
|
||||
The most simplest of doing error handling in rust is by returning `String` as a `Box<Error>`.
|
||||
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
## ErrorKind to the rescue
|
||||
# ErrorKind to the rescue
|
||||
|
||||
[TBD]
|
||||
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
## Debug for the ErrorKind
|
||||
# Debug for the ErrorKind
|
||||
|
||||
[TBD]
|
||||
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
## Simple Chained String Errors
|
||||
# Simple Chained String Errors
|
||||
|
||||
Now with the help of the `chainerror` crate, we can have a nicer output.
|
||||
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
## Mapping Errors
|
||||
# Mapping Errors
|
||||
|
||||
Now let's get more rust idiomatic by using `.map_err()`.
|
||||
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
## Saving coding chars
|
||||
# Saving coding chars
|
||||
|
||||
Because decorating an error with more information should not
|
||||
let you jump through hoops, `chainerror` has a quick macro for that.
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
## The source() of Errors
|
||||
# The source() of Errors
|
||||
|
||||
Sometimes you want to inspect the `source()` of an `Error`.
|
||||
`chainerror` implements `std::error::Error::source()`, so you can get the cause of an error.
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
## Downcast the Errors
|
||||
# Downcast the Errors
|
||||
|
||||
[TBD]
|
||||
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
## The root cause of all Errors
|
||||
# The root cause of all Errors
|
||||
|
||||
[TBD]
|
||||
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
## Finding an Error cause
|
||||
# Finding an Error cause
|
||||
|
||||
[TBD]
|
||||
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
## Selective Error Handling
|
||||
# Selective Error Handling
|
||||
|
||||
[TBD]
|
||||
|
||||
|
|
Loading…
Reference in a new issue