panic-log 0.3.0

Log panics to the `log` macro as error
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
26
27
28
29
30
31

# 🚨 panic-log

[![Actions Status](https://github.com/Traverse-Research/panic-log/actions/workflows/ci.yml/badge.svg)](https://github.com/Traverse-Research/panic-log/actions)
[![Latest version](https://img.shields.io/crates/v/panic-log.svg?logo=rust)](https://crates.io/crates/panic-log)
[![Documentation](https://docs.rs/panic-log/badge.svg)](https://docs.rs/panic-log)
[![MSRV](https://img.shields.io/badge/rustc-1.74.0+-ab6000.svg)](https://blog.rust-lang.org/2023/11/16/Rust-1.74.0.html)
[![Lines of code](https://tokei.rs/b1/github/Traverse-Research/panic-log)](https://github.com/Traverse-Research/panic-log)
![MIT](https://img.shields.io/badge/license-MIT-blue.svg)
[![Contributor Covenant](https://img.shields.io/badge/contributor%20covenant-v1.4%20adopted-ff69b4.svg)](./CODE_OF_CONDUCT.md)

[![Banner](banner.png)](https://traverseresearch.nl)

A simple crate that allows you to write the panic message and backtrace to the output of the `log` macro as `error`, while providing
the possibility to keep the original panic hooks.

## Usage

Add this to your Cargo.toml:

```toml
[dependencies]
panic-log = "0.3.0"
```

Call this somewhere at the start of your program (after initializing your logger):

```rust
use panic_log::Configuration;
[...]
panic_log::initialize_hook(Configuration::default());
```