Closed elliot-100 closed 4 weeks ago
I think it is pretty obvious that those functions are not meant to be public, so if anyone have used them in 3. party code, they should not be surprised if they change. So to me it sounds reasonable to prefix them with _ and don't worry about breaking anything.
I think these members shouldn't be used by end-users and therefore should be prefixed with
_
:I think this one should be moved:
as
spond.base
should only contain the internal_SpondBase
class.I am not sure if this should be considered a breaking change.
But once we have done this, I think we probably have the correct public API, and so will make it clearer in future: