Consider replacing `log` with `tracing`

[luisschwab]

tracing is a lot more versatile for downstream consumers and ecosystem support is better.

[luisschwab]

cc @satsfy

[tnull]

Which crate are you requesting this for exactly?

tracing's dependency story is unfortunately not as minimal as log's, so not sure if we'd consider switching to it for bitreq.

[luisschwab]

Personally, just bitreq. But it would be nice to replace it everywhere. Pretty much any Rust project already has tracing in the dep tree, so it's not a big deal. We could also have a macro that uses either log or tracing depending on a feature, for example.

[satsfy]

Argument for: the user can parse logs, and it would help trace async problems.

Argument against: our logs are simple, and the consumer can simply bridge the logs to tracing atm.

Personally, I don't find sufficient reason to do it for the project at this moment. However, with the production async client coming soon, it may become relevant as a broader logging overhaul follow-up. Worth tracking.