On Tuesday, 13 March 2018 at 02:06:57 UTC, psychoticRabbit wrote:
Mmm.. I don't think I like it.I feel you should be able to make a member of a class, private, regardless of where the class is located. This seems to break the concept of class encapsulation.No. I don't like it at all.
If you have access to the module source, you have access to the source of types inside it. Making the module the lowest level of encapsulation makes sense from that perspective.