mirror of
https://github.com/tokio-rs/tokio.git
synced 2026-08-26 00:00:16 +02:00
## Motivation `tokio-trace` should have static verbosity level filtering, like the `log` crate. The static max verbosity level should be controlled at compile time with a set of features. It should be possible to set a separate max level for release and debug mode builds. ## Solution We can do this fairly similarly to how the `log` crate does it: `tokio-trace` should export a constant whose value is set based on the static max level feature flags. Then, we add an if statement to the `span!` and `event!` macros which tests if that event or span's level is enabled. Closes #959
47 lines
1.1 KiB
TOML
47 lines
1.1 KiB
TOML
[package]
|
|
name = "tokio-trace"
|
|
version = "0.0.1"
|
|
authors = ["Eliza Weisman <[email protected]>"]
|
|
license = "MIT"
|
|
repository = "https://github.com/tokio-rs/tokio"
|
|
homepage = "https://tokio.rs"
|
|
description = """
|
|
A scoped, structured logging and diagnostics system.
|
|
"""
|
|
categories = ["development-tools::debugging", "asynchronous"]
|
|
keywords = ["logging", "tracing"]
|
|
|
|
# Not yet ready for production.
|
|
publish = false
|
|
|
|
[dependencies]
|
|
tokio-trace-core = "0.1"
|
|
cfg-if = "0.1.7"
|
|
|
|
[dev-dependencies]
|
|
ansi_term = "0.11"
|
|
humantime = "1.1.1"
|
|
futures = "0.1"
|
|
log = "0.4"
|
|
|
|
[features]
|
|
max_level_off = []
|
|
max_level_error = []
|
|
max_level_warn = []
|
|
max_level_info = []
|
|
max_level_debug = []
|
|
max_level_trace = []
|
|
|
|
release_max_level_off = []
|
|
release_max_level_error = []
|
|
release_max_level_warn = []
|
|
release_max_level_info = []
|
|
release_max_level_debug = []
|
|
release_max_level_trace = []
|
|
|
|
# These are used for the "basic" example from the tokio-trace-prototype repo,
|
|
# which is currently not included as it used the `tokio-trace-log` crate, and
|
|
# that crate is currently unstable.
|
|
# env_logger = "0.5"
|
|
# tokio-trace-log = { path = "../tokio-trace-log" }
|