dbg macro: Discuss use in tests, and slightly clarify
Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
This commit is contained in:
parent
2fb1dee14b
commit
a173518ceb
1 changed files with 4 additions and 3 deletions
|
@ -185,9 +185,10 @@ macro_rules! eprintln {
|
|||
/// builds or when debugging in release mode is significantly faster.
|
||||
///
|
||||
/// Note that the macro is intended as a debugging tool and therefore you
|
||||
/// should avoid having uses of it in version control for long periods.
|
||||
/// Use cases involving debug output that should be added to version control
|
||||
/// are better served by macros such as [`debug!`] from the [`log`] crate.
|
||||
/// should avoid having uses of it in version control for long periods
|
||||
/// (other than in tests etc.)
|
||||
/// Debug output from production code is better done with other facilities
|
||||
/// such as the [`debug!`] macro from the [`log`] crate.
|
||||
///
|
||||
/// # Stability
|
||||
///
|
||||
|
|
Loading…
Add table
Reference in a new issue