Some interesting holes in that spec: > What to do with leaks out of temporaries? : p = (s1 + s2).c_str(); > pointer/iterator invalidation leading to dangling

Some interesting holes in that spec: > What to do with leaks out of temporaries? : p = (s1 + s2).c_str(); > pointer/iterator invalidation leading to dangling pointers I feel like those are relatively common memory safety pitfalls, not obscure corner cases. The Core Guidelines have been in the works for about 7 years, I think? It's not clear if/when these will ever be addressed if they haven't been addressed by now. https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#to-do-unclassified-proto-rules https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines... There are other things mentioned in the list that look suspicious, but they're less clear. So, unless I'm misreading this, then I stand behind my original assertion that there is no safe subset of C++, but the Core Guidelines are certainly better than nothing... assuming they're actually used/enforced in real world applications. Other people are welcome to have their own opinions.