On Saturday, 4 June 2022 at 12:57:16 UTC, zjh wrote:

Encapsulation is very very important, At any level. you don't want class encapsulation and don't think it's worth it?

On Friday, 3 June 2022 at 12:06:01 UTC, zjh wrote:

it adds more special cases to metaprogramming for practically no benefit.

On Saturday, 4 June 2022 at 13:37:18 UTC, Commander Zot wrote:

Language is inherently complex.Obviously, d did not distinguish between module level encapsulation and class encapsulation. Finally, you told me that this will added "special cases".

On Saturday, 4 June 2022 at 13:41:43 UTC, zjh wrote:

If you dare not face the problem directly, you will only get more and more problems.

On Saturday, 4 June 2022 at 13:41:43 UTC, zjh wrote:

Well, that is a problem, as the main selling point is to be simpler than C++!!

On Saturday, 4 June 2022 at 13:56:07 UTC, Ola Fosheim Grøstad wrote:

If you want to meet the needs of more and more users, you must be complex.
Otherwise, you are cheating.

On Saturday, 4 June 2022 at 14:08:24 UTC, zjh wrote:

More and more users are using Python… Cheating pays off!

On Saturday, 4 June 2022 at 14:08:24 UTC, zjh wrote:

class private does not provide anything you can not already express in D.
if you don't want access to you class, put it in it's own module where it belongs.
but really this problem should not arise in the first place, because you should use interfaces anyway. a class should be an implementation detail.
if anything we could add the ability to declare multiple modules in one file, but i'm not a fan of that either.

On Saturday, 4 June 2022 at 14:21:41 UTC, Ola Fosheim Grøstad wrote:

Cheating first feel good, but then it all fell into bad luck.

On Saturday, 4 June 2022 at 14:23:42 UTC, Commander Zot wrote:

For me, it would be better ,if I could encapsulate at class level.In any case, I don't want the outside to affect my class inside.