dumblob

> Of course, Python modules don't have name collisions between class members and other stuff -- exactly because they use explicit `self` :) No, I meant only variable names, not...

> It's not unclear. It's just that there is little point in dividing classes and wrapped types since they are intermixed anyway. That's why using the same notation would make...

> How about removing `protected` and use `private` as the current `protected`? I feel `private` matches better with `public`. Sounds logical and feels good. I'm though very curious about the...

Maybe @Night-walker is talking more about the implementation - i.e. make the class smaller by putting thestatic data to a namespace. But I doubt there will be some performance gain.

I checked Go and there are no static variables (but I agree, that it's not directly comparable to the situation in Dao). I imagined myself deciding whether to put a...

>The choice was made to simplify the implementation, otherwise, we will need to add a dedicated virtual instruction or modify the `DVM_TUPLE` instruction for this. But if this is too...

@RobLoach yep, it wouldn't be a piece of cake - but probably not much more difficult than for retained UIs if you think of it (of course, you must not...

I'm sorry for us not getting earlier to this. I think this PR is quite valuable and was a lot of work to put it all together. We should merge...

I've skimmed it (really no review yet) and it actually looks surprisingly good to me. @RobLoach could you please thoroughly review it? @Hejsil would you also find some time to...

@Nielsbishere yep, we thought that merging small changes will make it more appropriate. As it turns out, not all the changes are as small as anticipated. Do you think you...