Using closure in function scope to make "real" private class members

[forkit]

On Tuesday, 7 June 2022 at 23:59:42 UTC, forkit wrote:
>
> Yes. I agree. @private is not descriptive enough.
>
> private(module) on the otherhand, states its purpose very 
> clearly.

On second thoughts - even private(module) is confusing. Does it 
mean private to the module? It's too confusing also.

Perhaps: private(this)  .. since 'this' is already traditionally 
associated with the abstraction it's referring to.