But they’ve decided to go in a different direction, I’m not sure what it is but I’ve been told on Scala issues that they’re working on it in this branch:
But it looks like the first things they’re attacking are the false positives of warnings, which are everywhere. I notice this since I used to compile with -Xfatal-warnings, but the false positives mean you can’t have a Short inside of a case class, for example.
I’m most excited about the style checker. It would be great to standardize on style.
I am too. I know Odersky has mentioned my WartRemover project a few times:
https://github.com/typelevel/wartremover
But they’ve decided to go in a different direction, I’m not sure what it is but I’ve been told on Scala issues that they’re working on it in this branch:
https://github.com/adriaanm/scala/tree/report-filter
But it looks like the first things they’re attacking are the false positives of warnings, which are everywhere. I notice this since I used to compile with
-Xfatal-warnings, but the false positives mean you can’t have a Short inside of a case class, for example.How do I get the compiler to warn/fail when someone uses
Option.get? This bit me this morning, I wish it was completely removed from Scala entirely.I have a rule for that in WartRemover, it’s pretty easy to enable:
https://github.com/typelevel/wartremover/blob/master/src/main/scala/wartremover/warts/OptionPartial.scala#L13