[flagged]
Seems a bit odd to go out of your way to bash rust evangelists on a completely unrelated thread, especially when the nobody in the comments has mentioned rust at all.
I have literally never seen this on a post not about memory corruption issues.
That came out of the blue for me, and offered no way for me to correct my behavior since he didn't make specific what he was really angry about.
I think it's the same story. Anti-Rustaceans get mixed up about why they reacted as they reacted. I'm guessing that in reality they had just reacted to the cultish/superior tone of some lone Rustacean at some point, but that's hard to put into words, so instead they generate the world-description that "there's evangelists everywhere" even though that wasn't what initially made them mad.
The original problem still lies with the Rustacean of course.
So e.g. there are some logic bugs where you're like yeah, I'd totally write that same bug in Rust but there are also arithmetic bugs where the problem arises because C++ inherits C's um, exciting "integer promotion" rules and Rust doesn't have those, far more of such situations in a Rust codebase are going to cause a puzzled programmer to investigate what really is going on with these integers and not write the bug.
Or there are type safety bugs where in Rust that mistake just won't compile, but in C++ it will compile it just has astonishing results. Obviously you can't write those bugs in Rust.
There's also a lot of contribution from ergonomics considerations where Rust's "Empowering everyone" idea means they think about library and feature design not just from the perspective of an expert but also a beginner, someone learning or maybe familiar with the rest of the language but not this particular feature. In C++ sort() is the unstable sort, if you don't know what unstable sorting is, you're given no clue that this might have consequences which astonish you. In Rust that sort is still there, but it's named sort_unstable() -- cuing a novice to read up about this idea before they are surprised. If they just write sort() they get a stable sort instead.