Tomek Sowiński wrote: > Can anyone give a good counter-example when a public alias of a > non-public symbol is evil?
I thought of two myself:) 1. Should class invariants be called for a public alias of a private method? 2. From D page: "A class can be exported, which means its name and all its non-private members are exposed externally to the DLL or EXE." - so a non- private alias of a private member gets exposed or not? I think there'd be a similar issue for D interface/header files. Tomek
