Hacker News new | ask | show | jobs
by dbalatero 346 days ago
Only by being a statistically different code base, unless you think this is a memory safety bug?
3 comments

Looking at the various issues reported in this thread, it honestly seems that burning the entire codebase and rewriting it would be the best choice. Bonus points for using a modern systems programming language.
Safety in rufst is not only about memory safety. It’s also about avoiding unpredictable behavior.
reading through the report, it's not unlikely to be a race condition