I do not have this impression. As for managing lifetimes in modern C++ I've already stated elsewhere that from my personal experience this problem practically does not not exist for application level programming. People writing OS level code will of course disagree but luckily I am not in that domain. I do write code for low power microcontrollers but I use plain C and do not have any real problems as there are no allocations / freeing. Just be careful with interrupts when handling shared data.
Comments
In C++ or C, you are always twisting the brain of the programmer into being a "safe compiler". I don't think that is an advantage personally.
Lifetimes don't go away just because there isn't a borrow checker or way to define them in the source code.
I do not have this impression. As for managing lifetimes in modern C++ I've already stated elsewhere that from my personal experience this problem practically does not not exist for application level programming. People writing OS level code will of course disagree but luckily I am not in that domain. I do write code for low power microcontrollers but I use plain C and do not have any real problems as there are no allocations / freeing. Just be careful with interrupts when handling shared data.
This isnt quite true, you can have memory-safe single ownership without borrow checking, and it feels quite different than what Rust has us do.