Re: C++ Memory Safety?
Thirdly, static analysis is a process prone to raising "consessions", places where there has to be some dialogue between dev and review to say why this static analysis whinge can be ignored. There's nothing formal in the syntax to say "here we are unsafe",
If we're talking compiler checks:
#pragma warning disable/restore
#pragma message
Otherwise the static analysis tool will allow you to disable particular static analysis whinges.
The point is that, to make C++ memory safe there's an awful lot of holes to plug, including in places you can't get to.
Follow modern design patterns and use compiler checks and static analysis tools to enforce them. No, you can't "get to" libraries without source code but you can't in Rust anyway. If you can "get to" libraries with source code then you can run static analysis on the library too and fix flags which are raised, which is more practical then rewriting whole libraries in Rust and causing a whole new set of bugs.