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?
3 replies 0 retweets 14 likesShow this thread -
Replying to @propensive
Call it `Internal` and put it all in there? Are we Haskell now? (I actually like that idea though)
1 reply 0 retweets 2 likes -
Replying to @reibitto @propensive
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
1 reply 0 retweets 2 likes
Good question. If Scala adopted it, it would mean dropping support for Java 8, wouldn't it? I don't think Scala could make it optional, but I don't really know much about Jigsaw...
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.