← Back to context Comment by michaeljx 10 months ago Could it be a memory related bug, which would not have existed in a memory safe language like Rust? 1 comment michaeljx Reply strstr 10 months ago You are probably saying this as a troll, but I’ll bite. I mean, sure Rust would have helped.Technically, the borrow checker and bounds checks wouldn’t have done it here (I’m aware I’m being obtuse by not just linking the bug).Having cleaner types and abstractions would almost certainly have solved the problem though. Normal C++ would have worked as well as Rust.
strstr 10 months ago You are probably saying this as a troll, but I’ll bite. I mean, sure Rust would have helped.Technically, the borrow checker and bounds checks wouldn’t have done it here (I’m aware I’m being obtuse by not just linking the bug).Having cleaner types and abstractions would almost certainly have solved the problem though. Normal C++ would have worked as well as Rust.
You are probably saying this as a troll, but I’ll bite. I mean, sure Rust would have helped.
Technically, the borrow checker and bounds checks wouldn’t have done it here (I’m aware I’m being obtuse by not just linking the bug).
Having cleaner types and abstractions would almost certainly have solved the problem though. Normal C++ would have worked as well as Rust.