Limin Fu

More precisely, it is incremental when the program is running in single threaded mode, and switches to concurrent GC once the program starts to run in multithreaded mode. It is...

> I can only suggest inspecting the GC structure and maybe other global stuff for signs of false sharing. For GC structure, not much can be done for this, because...

> I realized, that guys from Go finally decided to speed up their GC and make it "predictable" in terms of latency. There are three scenarios for Dao GC: -...

I am afraid that `import Mixin for Target` does not reflect the fact that the decorator methods of `Mixin` should be automatically applied to the methods of `Target`, and its...

> Speaking about clarity, if one hasn't ever encountered such feature, neither of the syntax variant will explain its meaning just by themselves. But getting rid of aspect classes would...

> I'm just looking for a way to make the language simpler and easier to reason about, particularly by erasing various magic entities whose scope seems too narrow to keep...

Also `aspect` could imply more things, there is really no way we will support them all. On the other hand, `import-in`, once made clear, won't drag in any extra things.

> 'Traditional' AOP, the one with aspects, is a rather marginal programming paradigm built around ad-hoc function hooks. I also felt that AOP in some languages is quite ad-hoc. Not...

> In Dao, I believe, the import-in will shift the archaic thinking about AOP a little bit higher. Let's hope so.

I am starting wonder if we really need support `for` patterns for classes and methods. I don't find it particularly useful. Automatic application of decorator methods to methods with the...