Unsound usages of unsafe implementation leading to potential use-after-free bug about curl-rust

[alexcrichton]

It's true that the return value of slice::from_raw_parts has an unbounded lifetime, but it is structurally only in use for the call of slice.to_vec() and is dynamically not accessed after that call. Given that while this has the possibility of UB I don't believe that it is directly, but that also sort of depends on exactly how you slice and dice unsafe Rust's guarantees. If you're able to model this in something like MIRI I think that would be great (it won't run as-is as I doubt MIRI knows about curl-the-system-library), but otherwise I think this is likely benign (unless you know of a concrete case where this is causing problems?)

[llooFlashooll]

I see, thanks for your instructive reply! It really depends on the case.