In Elixir especially, with everything being immutable, I don't really have to worry about state hanging around for my private methods to care about. I wind up just throwing private functions into little helper modules that can be tested independently.
As far as benefit of something being private, an API does not have to be maintained if it is private. Once it's out there, you're locked into doing that for the duration of your deprecation window.
Re:Elixir v1.4.0 released
by preordained on Thursday January 05, 2017 @12:21AM
(#13324967)
There are plenty of times. Take a data structure like a hashmap. You know there are plenty of internal functions to manage the map (rehash, handle collisions...) that there is no reason for a hashmap end user to see or even be tempted to muck with. Now, you can could make a new class as an interface to this hashmap with only the appropriate exposed methods...but that seems like an excessive sort of pattern.
In a statically typed language like Java, etc., it also gives you the benefit that when you are auto-completing or discovering methods, you see only the exposed methods you are meant to call as an API user instead of poring over every two-line helper method in the class.
Re:Elixir v1.4.0 released
by true_religion on Thursday January 05, 2017 @02:08AM
(#13325332)
When I subclass hashmap, I may desperately want to reimplement collision handling without also having to rewrite the every other private function it calls. Private functions close the library off to custom extension.
... and keeps the library's updates smoother, since there can't be any tinkering with library's implementation.
Re:Elixir v1.4.0 released
by true_religion on Friday January 06, 2017 @12:32PM
(#13338225)
You don't have to support users who use your library internals. Django for instance didn't support everyone who relied on undocumented internals in its orm. The standardization for the latest release made those internals clean and documented, but unapologetically broke other people's code including mine.
Private functions permit functional decomposition without a commitment to support the interface implemented by the private functions (meaning the functions can be changed / refactored without breaking clients of the library).
They seem quite useful. Mostly signaling that things should not be used.
What's the largest number of people you've workwe with on a codebase? I would assume the benefits aren't really all that much for small codebases / teams.
Re:Elixir v1.4.0 released
by brightball on Thursday January 05, 2017 @08:29AM
(#13326925)
On a single code base, the most I've worked with at a time is 12.
Professionally I've never seen a private function/method that had a purpose or benefit from being private.