Limin Fu

> But there still is a case when some method is left not implemented. For non-interface methods, it is preferable to raise compile-time error in this case. That would be...

The casting on lists (and maps) is done in element-wise, so you can cast empty list to any other type of list.

OK, now there are bugs.

> 1) Throw async classes overboard (#393). There is a dedicated issue in which the arguments are presented, so I don't stop here. We will discuss that there. > 2)...

> I'm though very curious about the confusion when mixing dao classes and e.g. C++ wrapped classes I don't see the confusion, because wrapped C++ classes has no private members,...

> That seems like yet more rules to follow, no? Not very intuitive if I got it correctly. The rule is actually very simple and logical: there should be no...

> Placing global variable together with the related class into a separate namespace while exporting only the class should resolve all the issues you mentioned. What's the advantage of doing...

> Maybe @Night-walker is talking more about the implementation - i.e. make the class smaller by putting thestatic data to a namespace. It will make little difference.

> Static variables hidden within functions and classes are easier to overlook. That can be easily fixed. We can require explicit class name prefix for using such variables anywhere. >...

> And absence of global state is even better :) We cannot avoid global state, otherwise, the interactive mode will become useless. > 7) Make inherited/mixed-in members accessible only as...