How to Get a Very Firefully Safe C++

The assumption here, the fundamental assumption is that safety is not one thing. My favorite of course is the usual type and resource safety. It's not just type safe. If you leak resources, your system stops. That's not a good idea. So we need both type safety andresource safety. We don't leak. And there's some design for that. And they've been prototyped in the core guidelines which you can go and use. But it's not perfectly implemented partly because people haven't focused on it.