On Wednesday, 15 February 2023 at 09:57:56 UTC, ProtectAndHide
wrote:
In a module that contains a class, and other code as well
(perhaps other tightly coupled classes), you can know
**nothing** at all about that type (or any other class) without
knowing **everything** else in the module. If one understands
this, then one understands the problem here ;-)
.. btw. other code.. includes unitests as well.
The solution that D provides, is not a solution. It's a design
constraint being forced on programmers. Anyone that argues
otherwise, is speaking out of their ...
Right... They greatly increase your code maintenance work!
