Re:Rust’s standard library was vulnerable for years and nobo...
by dbaupp on Saturday February 16, 2019 @03:47PM
(#19180845)
That 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.)
"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."