Samuel Moelius
Samuel Moelius
> For that matter miniz_oxide could probably benefit being moved/transfered to an org or something FWIW, `miniz_oxide` appears in my projects' dependency trees under [`anyhow`](https://github.com/dtolnay/anyhow) >> [`backtrace`](https://github.com/rust-lang/backtrace-rs/tree/master) and [`gix`](https://github.com/Byron/gitoxide) >>...
@Shnatsel Are there any "gotchas" you would anticipate, were someone to try to implement this?
At the risk of feature creep, it might be good to warn about `println!("... {} ...", path.to_string_lossy())` also.
Thanks, @davvid!
> If you are "panic!" in your script then flamegraph won't build the svg And similarly if you are using `std::process::exit` (which was my mistake).
> While I'm here we should migrate those compile tests to `trybuild` eyes May I ask, what benefit would this provide? (This is a serious question, BTW.)
Thanks, @KodrAus. I would be curious to see what those changes would look like.
> Format as binary, but line-by line. So weird characters are visible as escapes, but multi-line text output is readable Is the idea that a linebreak would be added after...
I have a prototype working, but admittedly the boundaries between `stdout`, `stderr`, etc. become hard to find when the number of lines is large. I can see at least six...
Just a thought: maybe `--nocapture` would make a difference(?).