As someone who programs both C++ and Rust, without even reading the article, my own experience with typos in those languages is:

Rust: Typo? Now it just doesn't compile anymore. Worst case is that the compiler does a bad job at explaining the error and you don't find it immediately.

C++: Typo? Good luck. Things may now be broken in so subtle and hard to figure out ways it may haunt you till the rest of your days.

But that of course depends on the nature of the typo. Now I should go and read the article.

> Worst case is that the compiler does a bad job at explaining the error and you don't find it immediately.

By the way, the project considers this a bug and accepts reports for that. In many occasions they are easy to fix. In others large refactors are needed. But being aware of the case is the necessary first step to making them better.