Skip to content

Commit ea9e2b9

Browse files
authored
Merge pull request GitoxideLabs#2401 from GitoxideLabs/improvements
fix: use `tracing` instead of `tracing-core` to re-use the standard macros.
2 parents e8612b5 + 7166aaf commit ea9e2b9

File tree

4 files changed

+42
-330
lines changed

4 files changed

+42
-330
lines changed

Cargo.lock

Lines changed: 3 additions & 3 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

gix-trace/Cargo.toml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -20,18 +20,18 @@ test = false
2020
## Note that there is no default feature, as the application is supposed to opt-in via `gix-features` or using this crate directly.
2121
default = []
2222

23-
## Implement `tracing` with `tracing-core`, which provides applications with valuable performance details if they opt-in to it.
23+
## Implement `tracing` with the `tracing` crate, which provides applications with valuable performance details if they opt-in to it.
2424
##
2525
## Note that this may have overhead as well, thus instrumentations should be used stategically, only providing coarse tracing by default and adding details
2626
## only where needed while marking them with the appropriate level.
27-
tracing = ["dep:tracing-core"]
27+
tracing = ["dep:tracing"]
2828

2929
## If enabled, detailed tracing is also emitted, which can greatly increase insights but at a cost.
3030
tracing-detail = []
3131

3232

3333
[dependencies]
34-
tracing-core = { version = "0.1.36", optional = true }
34+
tracing = { version = "0.1.44", optional = true, default-features = false, features = ["std"] }
3535

3636
document-features = { version = "0.2.0", optional = true }
3737

0 commit comments

Comments
 (0)