File tree Expand file tree Collapse file tree 1 file changed +3
-3
lines changed Expand file tree Collapse file tree 1 file changed +3
-3
lines changed Original file line number Diff line number Diff line change @@ -40,12 +40,12 @@ There are five macros that the logging subsystem uses:
4040* `warn!(...)` - a macro hard-wired to the log level of `WARN`
4141* `error!(...)` - a macro hard-wired to the log level of `ERROR`
4242
43- All of these macros use std:: the same style of syntax as the `format!` syntax
43+ All of these macros use the same style of syntax as the `format!` syntax
4444extension. Details about the syntax can be found in the documentation of
4545`std::fmt` along with the Rust tutorial/manual.
4646
4747If you want to check at runtime if a given logging level is enabled (e.g. if the
48- information you would want to log is expensive to produce), you can use std:: the
48+ information you would want to log is expensive to produce), you can use the
4949following macro:
5050
5151* `log_enabled!(level)` - returns true if logging of the given level is enabled
@@ -63,7 +63,7 @@ path::to::module=log_level
6363
6464The path to the module is rooted in the name of the crate it was compiled for,
6565so if your program is contained in a file `hello.rs`, for example, to turn on
66- logging for this file you would use std:: a value of `RUST_LOG=hello`.
66+ logging for this file you would use a value of `RUST_LOG=hello`.
6767Furthermore, this path is a prefix-search, so all modules nested in the
6868specified module will also have logging enabled.
6969
You can’t perform that action at this time.
0 commit comments