You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
neqo* currently uses neqo_common::log for all things logging. It is a wrapper around the log crate.
What is the benefit of using neqo_common::log over using the log crate directly? From what I can tell:
neqo_common::log does not require explicit instantiation of the logger (e.g. via env_logger::init) but instead tries to initialize on each log invocation.
neqo*
currently usesneqo_common::log
for all things logging. It is a wrapper around thelog
crate.What is the benefit of using
neqo_common::log
over using thelog
crate directly? From what I can tell:neqo_common::log
does not require explicit instantiation of the logger (e.g. viaenv_logger::init
) but instead tries to initialize on each log invocation.neqo/neqo-common/src/log.rs
Lines 84 to 90 in c209c43
neqo/neqo-common/src/log.rs
Lines 69 to 71 in c209c43
Are the benefits worth a custom way of logging? Should a library instantiate a logger instead of the conventional instantiation by the calling binary?
Related, other Mozilla code using
log
:https://searchfox.org/mozilla-central/search?q=%5Elog+%3D&path=*Cargo.toml&case=true®exp=true
The text was updated successfully, but these errors were encountered: