Alec Mocatta

Ah, I see what you mean. I think this is possible without adding any lines: ```rust // from raw to st::Box let raw: *mut T = ...; let st_box: st::Box...

> Panicing while unwinding _may_ cause the process to abort, but you cannot rely on it for soundness Huh, thanks for raising this! For reference, the best (and only) docs...

Good question! Short answer: No, this approach is not yet secure against malicious actors. However, if we assume non-malicious actors and typical (static or dynamic) linking conditions, then it's not...

@gretchenfrage I'd love to hear if you've made any progress on that?

I was under the impression that IndexMove was consuming the container: `fn index_move(self, index) -> Self::Item`, such that one could use ``` vec[i] ``` rather than the current nicest way...

@alexreg It is equivalent to the extent that it returns a `T` without requiring `Copy`/`Clone`. It differs in that `remove` takes `&mut collection`, and does does nontrivial work – shifting...

For many/most uses the size savings of `unwrap_throw` aren't worth the extra debugging cost. In my case it was giving opaque errors, as well as triggering UB that led to...

Thanks @weihanglo. For reference here's the corresponding issue in Nextest https://github.com/nextest-rs/nextest/issues/174