std::dbg panics on failure, given dbg! is advertised as "quick n' dirty" I think this behaviour makes sense here too (no need to type .unwrap() everywhere, no unused Result warnings)
also to be more analogous, actually use heprintln (as already advertised in documentation)
I went ahead and added the nod to 2018 edition missing last time
I'm sorry, it's me again...
dbg!
is advertised as "quick n' dirty" I think this behaviour makes sense here too (no need to type.unwrap()
everywhere, no unused Result warnings)heprintln
(as already advertised in documentation)