-
Kind of getting off topic but I agree with you that static analysis for JVM dependency linking is a really promising avenue. I hope we'll see more development in this area in the future. Have you seen https://github.com/spotify/missinglink ?
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
The SBT plugin is at https://github.com/scalacenter/sbt-missinglink
-
http4s is the worst web server on the JVM. It's very slow. It suffers from NIH syndrome so has a poor feature set. And you see code like this to do basic things like authentication e.g.
-
The good news is that scaladoc is produced by default by sbt and published by default. So you can often pull it from the same repository your library jar came from, extract it with zip, and read the docs. But that's also totally unnecessary - javadoc.io allows you to put in your module info and serves the docs for you, so if there's an older version you can access the documentation this way. Rely on the type signatures, since they can't lie, whilst comments (including scaladoc comments) can. Honestly, library authors should be using mdoc and including examples on every public method, and that type of documentation is something you can almost always contribute to a project for a quick pr kudos.
-
Yeah, I think a cross compiler would be the only way such a thing could be possible. It would be interesting to see how many collections are actually changed though. I have written similar things using soot. The biggest question is whether there would be enough people who would want such a thing. I can't imagine the time savings vs time spent would pay off for me personally.
-
yep, nailed it: https://github.com/apache/spark/blob/master/pom.xml#L122
