> I see that repo is two years old If the repo is what I think it is, the underlying bug is over a decade old [0]. From what I understand the devs have known h

> I see that repo is two years old If the repo is what I think it is, the underlying bug is over a decade old [0]. From what I understand the devs have known how to solve it for pretty much this entire time, but their desired solution is blocked on some rather large refactorings elsewhere in the compiler. > are there flaws in Rust that aren’t edge cases that would make it not memory safe? cve-rs is probably the most well-known one, but it's definitely not the only one [1]. That being said, I think there's a not-unreasonable argument to be made that cve-rs counts as an edge case since (as far as I know) there's no publicly-known examples of code that has "organically" run into this. On a more practical note, I think if you're worried about memory safety in Rust code type system holes are vanishingly unlikely to be the cause compared to more "normal" things like mistakes in-around `unsafe` blocks. [0]: https://github.com/rust-lang/rust/issues/25860 https://github.com/rust-lang/rust/issues/25860 [1]: https://github.com/rust-lang/rust/issues?q=state%3Aopen%20label%3A%22I-unsound%22 https://github.com/rust-lang/rust/issues?q=state%3Aopen%20la...