Re: So far, the Rust coreutils pass approximately 500 out of 600 GNU tests
There seems to be a little cognitive dissonance in your reply. Your response to my suggesting that there is a big difference between two classes of bug is to first ask "Is there?" but then go on to say that one is "orders of magnitude worse" than the other, suggesting that there is.
The comment to which I was replying said "A 17% failure rate strikes me as being much too high ... Especially as Rust is promoted as something that reduces errors, by design." My point was that what's causing these tests to fail has little to do with the errors that Rust reduces by design. As I said, a 17% test failure rate in the functional compatibility testing is not acceptable as a final state, for precisely the reasons that you state. That's why the project explicitly treats any incompatibility as a bug and is diligently tracking its progress towards removing them all.
I'm unsure how you read into my reply some suggest that it's acceptable for core tools to behave slightly differently, especially when I just stated that it's not acceptable, but your final snark perhaps gives a clue. Many of the comments one reads about Rust seem to be obsessed with the idea that Rust programmers are obsessed with memory bugs to the exclusion of all else. I'm not a habitual Rust programmer, but I know many, and for the most part their goals (obsessions if you want) are around reliability, maintainability, portability and reusability, and they happen to find Rust a good tool for that particular job. The source code to GNU utils is just as arcane as the shell scripts that you mention. A rewrite whose explicit goal is 100% compatibility while being more portable and maintainable, and as it happens immune from certain classes of bug, seems like a worthwhile cause.