> The hard part is to select which features of C++ to use and more importantly which NOT to use and to ENFORCE these rules. Maybe I've just not kept up properl

> The hard part is to select which features of C++ to use and more importantly which NOT to use and to ENFORCE these rules. Maybe I've just not kept up properly, but I find it surprising that there isn't a tool which can enforce this already. It seems so obviously desirable. I guess clang-tidy + custom "checks" + CI server enforcement could achieve something similar, but I'm just surprised that it doesn't exist. (Of course, many of the useful metaprogramming libraries for C++, e.g. Boost::Hana, use a lot of weird features of C++ to achieve their goal of being simpler to use for clients of the library. I suppose it might be possible to limit the warnings to "self-implemented" functionality, but it might be tricky...)