debug printing conventions
In !514 (merged) I introduced and used this:
// Switch to the nontrivial version of this, to get debugging output on stderr
macro_rules! dprintln { { $f:literal $($a:tt)* } => { () } }
//macro_rules! dprintln { { $f:literal $($a:tt)* } => { eprintln!(concat!(" ",$f) $($a)*) } }
This is rather ad-hoc and not ideal. Other contributors report having done similar things, albeing usually only locally and not in proposed MR branches.
It would be better to have something more principled. We should consider tracing
and its release_max_level_info
feature, as per !514 (comment 2805304).
When we have an approach, in tree debugging code should then be changed to use that.