Matilde Morrone

I'd love to tackle this immediately as it's relatively straight foreword thing to do but it's probably better for #185 to be merged first otherwise we will drown in merge...

Another reason to consider splitting up the code is supporting other commands such as #107 although I'm not sure that it applies to cargo_metadata

But what is the reason to use utf8 paths? I don't see why utf8 paths should be used in this context. They don't seem to provide any benefits and I...

> serde_json will emit an error when you try to serialize a non-utf8 `Path`(`Buf`). If that's the case isn't camino even more redunant?

My main argument is that for anyone, like me, that doesn't need nor care about utf8 paths but really just wants a normal std path it doesn't actually had anything...

After reading the discussion in #152 I really agree with all of @matklad (forgive the ping) points execpt for the fact that I don't really have the luxury to fork...

I'd love add some test cases but I honestly don't know how to reproduce those crashes. I spend 90% of my time on linux and those crashes happened when testing...

I assumed Utf8PathBuf implemented all the methods from PathBuf but I see how that can be a problem especially with third-party impls. Is there a better solution to make camino...

Yeah I see how that's a big very big issue. Maybe a better solution is a wrapper type kinda like [the map in serde_json](https://docs.rs/serde_json/latest/serde_json/struct.Map.html). But honestly I think camino should...

This would prove very useful but I am not sure what the status on this is on cargo considering that https://github.com/rust-lang/cargo/issues/8002 hasn't been updated since 2020