These are chat archives for sbt/sbt
A relaxed chat room about sbt (That interactive build tool). For getting help on sbt, we encourage people to document it on Stackoverflow or subscribing to Lightbend subscription.
import foo._, blahinstead of
import foo, foo.blah, type aliases, use of invisible method names like apply(), lack of comments, stuff like that. I think modularity will be helpful myself but the difficulty of the codebase for me is mostly that it's just a little too far on the "don't write things out explicitly" side of the fence. but then, I usually prefer verbose code. and verbose english.
right, so modularity doesn't help/hurt that aspect. It's orthogonal.
Still, I plan to cleanup, comment, etc. as we pull out modules. E.g. sbt/launcher is getting close to being ok on its own (see https://github.com/sbt/launcher). First step was documenting all the public APIs
sbt/utilor some such