Re:Practical Go: Real-world advice for writing maintainable ...
by int_19h on Thursday February 21, 2019 @11:02PM
(#19223022)
You are still leaking the details of the function that is the sole caller of those other functions. It's not leaking across translation unit boundary, but it's not the only one that matters.
For better or for worse, taking advantage of that forces you to keep source files fairly short and cohesive in functionality.