Kometes

@0:31:00: Wow, is there really a debate on what a module is? Just combine the outdated concept of header / source into one file -- that's a module. Now solve all the language problems that crop up. I agree it's a huge change, modules will have to exist side-by-side with the old system for backwards compatibility.

"#include file" is similar to "from file import *", always a bad idea.  C++ will need fine-grained symbol import/export control for macros, namespaces, templates, classes, functions and variables.  Look at Python for inspiration: "from module import symbol as local_symbol"

Of course "#include" does more than just import symbols, but the idea is to develop new language to divide its power until it's no longer needed; it's a sledgehammer of a directive and should be deprecated.

In response to lambda arg types at 49:00, I don't think it would be too much to ask for something like function_arity<T> and function_arg<T, int> to get the number and type of arguments of any regular/member/bind/lambda function.  I've written such a meta function for regular/member, but it's not possible for bind/lambda.

I'm surprised that the range-for, a language extension, made it into the standard when a beautifully composable library extension using for_each was *so* close to being realized.  Just need those polymorphic lambdas [&](auto& e) {...}