5 releases

0.3.3 Apr 24, 2024
0.3.2 Apr 23, 2024
0.3.1 Apr 22, 2024
0.3.0 Apr 22, 2024
0.2.0 Apr 22, 2024

#5 in #detail

Download history 116/week @ 2024-11-15 68/week @ 2024-11-22 3/week @ 2024-11-29 37/week @ 2024-12-06 106/week @ 2024-12-13 33/week @ 2024-12-20 32/week @ 2024-12-27 107/week @ 2025-01-03 186/week @ 2025-01-10 140/week @ 2025-01-17 253/week @ 2025-01-24 171/week @ 2025-01-31 234/week @ 2025-02-07 126/week @ 2025-02-14 170/week @ 2025-02-21 254/week @ 2025-02-28

825 downloads per month

Apache-2.0

16KB
197 lines

detailer

A convenience tool for workflow logging.

About

A trim, low-dependency tool for logging things. This project does not use unsafe code. It only depends on std and log.

Details

Detailer lets you log all your related information about a workflow in one log report. Sometimes you want that. Sometimes you only want that once in a while.

The overhead of a disabled Detailer log line is similar to the overhead of a disabled log level, like a log::debug!() when the current level is set to Info. An enabled detail!() statement costs a writeln!() into a String. If you want to keep this inexpensive and you have a ton of these detailers, you should consider using an explicit flush() and reuse them. Remember to reset() when your time should restart, if you are using timings.

use detailer::{Detailer, detail, new_detailer, scope};

let mut detailer = new_detailer!(); // Info level, WithTimings
detail!(detailer, "some {} message", "log");

You might consider taking a Detailer as a parameter for functions that should log detail when the detailer is enabled. The functions do not need to inspect the Detailer: They only log their details, similarly to how you use log.

fn expensive_work(detailer: &mut Detailer, name: &str) {
    let _guard = scope!(detailer, "expensive work: {name}"); // indent lines under the expensive_work stack
    detail!(detailer, "some part of the work");
    detail!(detailer, "some other part of the work");
}

Dependencies

~88KB