Description
Looks cool! However, the code out there is already implemented with tracing and log crates - I'd like those logs to be handled ad well.
Use Case
Have one logger implementation per executable that prints the logs from the whole ecosystem of crates, not just the statements written with sheen macros explicitly.
Possible Implementation
Implement adapters for log and tracing crates; in the tracing ecosystem this is called "subscriber", don't remember how it's called in the log ecosystem...
Description
Looks cool! However, the code out there is already implemented with
tracingandlogcrates - I'd like those logs to be handled ad well.Use Case
Have one logger implementation per executable that prints the logs from the whole ecosystem of crates, not just the statements written with sheen macros explicitly.
Possible Implementation
Implement adapters for
logandtracingcrates; in thetracingecosystem this is called "subscriber", don't remember how it's called in thelogecosystem...