Skip to content

Commit 341540b

Browse files
committed
doc: Mention 'debug' log level in tutorial. Closes #1579
1 parent 2d99103 commit 341540b

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

doc/tutorial.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -744,16 +744,16 @@ log(warn, "hi");
744744
log(error, (1, [2.5, -1.8]));
745745
~~~~
746746

747-
The first argument is the log level (levels `info`, `warn`, and
748-
`error` are predefined), and the second is the value to log. By
747+
The first argument is the log level (levels `debug`, `info`, `warn`,
748+
and `error` are predefined), and the second is the value to log. By
749749
default, you *will not* see the output of that first log statement,
750750
which has `warn` level. The environment variable `RUST_LOG` controls
751751
which log level is used. It can contain a comma-separated list of
752752
paths for modules that should be logged. For example, running `rustc`
753753
with `RUST_LOG=rustc::front::attr` will turn on logging in its
754754
attribute parser. If you compile a program named `foo.rs`, its
755755
top-level module will be called `foo`, and you can set `RUST_LOG` to
756-
`foo` to enable `warn` and `info` logging for the module.
756+
`foo` to enable `warn`, `info` and `debug` logging for the module.
757757

758758
Turned-off `log` statements impose minimal overhead on the code that
759759
contains them, so except in code that needs to be really, really fast,

0 commit comments

Comments
 (0)