4 ms·
I see no mention of memory safety or unsafety in the issue you linked. Could you be more specific?
by dbaupp 8y ago
I see no mention of memory safety or unsafety in the issue you linked. Could you be more specific?
- rurban 8y agoI don't need to be more specific. Read the ticket outlining the alloca problems. It cannot get more safety relevant. "Unresolved questions: * [ ] How can we mitigate the risk of unintended unsized or large allocas? Note that the problem already exists today with large structs/arrays. A MIR lint against large/variable stack sizes would probably help users avoid these stack overflows. Do we want it in Clippy? rustc? * [ ] How do we handle truely-unsized DSTs when we get them? They can theoretically be passed to functions, but they can never be put in temporaries."
- dbaupp 8y agoThat is a feature that is not yet implemented! Of course there may be unsolved questions. Neither of those are memory safety relevant. (A stack overflow is a reliable crash, not memory corruption, in Rust.)