spdlog/
re_export.rs

1//! Re-exports items from other crates for convenience.
2//!
3//! This module selectively re-exports items from other crates that may be used
4//! by users. This effectively eliminates the hassle of manually adding
5//! dependencies to the user's own `Cargo.toml`.
6//!
7//! Users can still call items from these crates directly, as long as semver
8//! versions of the dependencies are compatible.
9
10/// Items from [`log` crate].
11///
12/// The `log` crate has its own level filter, and logs produced by `log` crate
13/// macros will first be filtered by `log` crate itself (this is not controlled
14/// by `spdlog-rs`). When users enable the `log` crate compatibility layer
15/// proxy, please make sure that `log` crate's own level filter is configured
16/// appropriately so that `spdlog-rs` can receive logs.
17///
18/// - To enable the `log` crate compatibility layer proxy, call
19///   [`spdlog::init_log_crate_proxy`].
20///
21/// - To configure `log` crate's own level filter, call
22///   [`re_export::log::set_max_level`] with [`re_export::log::LevelFilter`].
23///
24/// [`log` crate]: https://docs.rs/log
25/// [`spdlog::init_log_crate_proxy`]: crate::init_log_crate_proxy
26/// [`re_export::log::set_max_level`]: crate::re_export::log::set_max_level
27/// [`re_export::log::LevelFilter`]: crate::re_export::log::LevelFilter
28#[cfg(feature = "log")]
29pub mod log {
30    pub use log::{set_max_level, LevelFilter, SetLoggerError};
31}