Doc: project readme could explain the benefits v.s. findbugs
It is possible to run findbugs on a scala codebase, since findbugs acts on bytecode. See e.g. https://github.com/sbt/findbugs4sbt It also seems to work tolerably well; I found a few bugs in my scala project (unclosed file handles) this way. However it does generate masses of false positives mostly around class and method naming conventions.
Is alacs a reimplementation of the findbugs bytecode scanner plus a ruleset optimised for Scala?
Is that expected to offer benefits not achievable by a project that just took the findbugs codebase and worked on Scala specific scanners and tweaked the existing findbugs scanners to reduce Scala specific false positives?
I assume that you've already considered this, but it seems likely to be a FAQ -- the project README could address this issue directly?