Since the Scala IDE experience is getting better at completions, API hygiene is becoming more important: users should not have to wade through lots of "incidental" methods and types to find the ones that are relevant to them.
Show this thread
More careful use of visibility modifiers can help to hide methods. But here's a question: would it be a reasonable approach to nest non-user-facing types (which can't be private) inside the companion objects of related, public types, as a way of making them less visible?
-
-
This is something that Java modules really help with. Perhaps Scala could make use of it (or something similar) to allow more granularity over which packages are exposed to end users vs to other modules of the same library or set of libraries.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Call it `Internal` and put it all in there? Are we Haskell now? (I actually like that idea though)
-
That reminds me to ask where Scala stand on adopting Java Module system? Sounds like a tool for this particular issue. But to work, you need to modularise everything
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.