mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

doc: Mention 'debug' log level in tutorial. Closes #1579

Browse Source
This commit is contained in:
Brian Anderson 2012-01-20 01:04:36 -08:00
parent 2d9910383e
commit 341540b694
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/tutorial.md
View File

@ -744,8 +744,8 @@ log(warn, "hi");
log(error, (1, [2.5, -1.8]));
~~~~
The first argument is the log level (levels `info`, `warn`, and
`error` are predefined), and the second is the value to log. By
The first argument is the log level (levels `debug`, `info`, `warn`,
and `error` are predefined), and the second is the value to log. By
default, you *will not* see the output of that first log statement,
which has `warn` level. The environment variable `RUST_LOG` controls
which log level is used. It can contain a comma-separated list of
@ -753,7 +753,7 @@ paths for modules that should be logged. For example, running `rustc`
with `RUST_LOG=rustc::front::attr` will turn on logging in its
attribute parser. If you compile a program named `foo.rs`, its
top-level module will be called `foo`, and you can set `RUST_LOG` to
`foo` to enable `warn` and `info` logging for the module.
`foo` to enable `warn`, `info` and `debug` logging for the module.
Turned-off `log` statements impose minimal overhead on the code that
contains them, so except in code that needs to be really, really fast,