oopsie 0.1.0-rc.4

Ergonomic, structured error handling: context selectors, traced errors, and rich colorized reports
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25

Marks this field as the packed `(Backtrace, SpanTrace)` pair, surfacing both
through `Diagnostic::oopsie_backtrace` and `oopsie_spantrace` from one field. The
type must be `(Backtrace, SpanTrace)` (optionally boxed); it is auto-captured and
excluded from the selector. A packed `traces` field cannot coexist with separate
`backtrace`/`spantrace` fields.

Forms: `traces`, `traces = true`, `traces = false`.

### Example
```
use oopsie::{Backtrace, SpanTrace};

#[oopsie::oopsie]
#[oopsie(module(false))]
pub enum AppError {
    #[oopsie("boom")]
    Boom {
        #[oopsie(traces)]
        traces: (Backtrace, SpanTrace),
    },
}

let err = Boom.build();
assert_eq!(err.to_string(), "boom");
```