3 ms·
In my experience the more things are public the better. Very often a quick workaround turns into a monster bodge because some method is marked strict private in
by magicalhippo 8y ago
In my experience the more things are public the better. Very often a quick workaround turns into a monster bodge because some method is marked strict private instead of protected or public.
So I usually make most stuff public as such, but put internals in a namespace/scope that makes it clear that these are implementation details. Relying on implementation details always carries the risk of breaking when upgrading.
This allows for a lot of flexibility when needed, while also not polluting the "truly public" API.