Pointers

If you do a search for something like "why is Rust safer than C++" you will find multiple examples of the fun ways we can screw ourselves in c/c++, lol.

Not specific functions, but as said elsewhere, the language is a mine field that too many joyfully walk upon.

Look up e.g. pointer aliasing. I'd bet most of my colleagues don't have a clue about that (not a risky bet given the crap they write). Thankfully compiler writers know the majority of their users are too lazy to learn the stupid standard in this case (I don't blame them). But not necessarily in other ones.

C++ is a tool designed for expert but used by everyone's Grandma, with the results you could expect.

There are many things in C++ that are “undefined behaviour”, UB (and several similar but technically different terms). These may or may not result in an error or warning at compile time. Worse, they usually lead to crashes or even seemingly random behaviour - even in code that is not directly tied to the UB.

The easiest example is memory management and pointers. You can create a new object and assign it to a variable. If you then delete the object, the variable could still point to the deleted object’s memory. And if you use that variable, that’s UB. It will likely crash, but probably not right away, which can be very hard to diagnose.

An interesting fact about UB is that optimisers may assume it does not exist. They can basically reason “well this code path would lead to UB, which can’t exist, so this code path can just be removed”. This could theoretically even affect code that runs before the UB.