#error #error-handling #composition #scalable #introspection #programmatic #most

no-std rancor

Scalable and efficient error handling without type composition

9 releases

0.1.0-pre8 Jan 1, 2024
0.1.0-pre7 Dec 15, 2023
0.1.0-pre1 Nov 4, 2023
0.1.0-alpha.9 Mar 30, 2024

#993 in Rust patterns

Download history 31/week @ 2024-01-01 15/week @ 2024-01-08 2/week @ 2024-01-15 1/week @ 2024-01-22 2/week @ 2024-01-29 2/week @ 2024-02-05 27/week @ 2024-02-12 39/week @ 2024-02-19 140/week @ 2024-02-26 29/week @ 2024-03-04 33/week @ 2024-03-11 268/week @ 2024-03-18 135/week @ 2024-03-25 205/week @ 2024-04-01 479/week @ 2024-04-08 366/week @ 2024-04-15

1,237 downloads per month

MIT license

24KB
515 lines

rancor

rancor provides scalable and efficient error handling without using type composition. This makes it best-suited for situations where:

  • Programmatic error introspection is not useful
  • Functions may error, but succeed most of the time
  • Errors should provide as much useful detail as possible when emitted
  • Use cases include both no_std and targets with support for std

lib.rs:

rancor

rancor provides scalable and efficient error handling without using type composition. This makes it best-suited for situations where:

  • Programmatic error introspection is not useful
  • Functions may error, but succeed most of the time
  • Errors should provide as much useful detail as possible when emitted
  • Use cases include both no_std and targets with support for std

Dependencies

~340–790KB
~19K SLoC