Closed zaczkows closed 1 month ago
I did something wrong, because it works without any features, but macro should fail...
hmmm... looks complex :disappointed:
making tracing dependency optional and using log instead
Those crates are not the same, and the choice of tracing
here is very intentional.
I think I understand the idea, but would then at least be ok to make tracing optional? I can imagine many applications that doesn't need or even want to have tracing.
I can imagine many applications that doesn't need or even want to have tracing.
This is the first time someone has expressed this need since this library was created, so there are probably not that many.
Having tracing
as optional could be accepted, but it'd have to be properly tested in CI.
Reduced scope as requested
Sorry for a delay, but all the changes should be there
This pull request is trying to reduce dependencies by:
tracing
dependency optional and usinglog
insteadI hope I did cfg correctly as I'm doing it first time