Scapegoat VS sbt-tpolecat

I've since figured this out (Scapegoat/FinalModifierOnCaseClass and WartRemover/FinalCaseClass). I plan to add it to the next version of the article.

The support for scala 3 has been requested a while ago: https://github.com/scapegoat-scala/scapegoat/issues/521 but the original author has stepped down as a maintainer https://github.com/scapegoat-scala/scapegoat/issues/567 and recently most of the changes are just dependency updates.

I'm awed by the maturity of the Scala 2 compiler. Every minor version in the 2.13 series adds a new linting improvement. You can see that if you have sbt-tpolecat in your project. I'm always happy to see that some option from Wartremover is no longer used.

Note that this assumes that non-Unit values are silently thrown away, which you should always configure scalac, preferably via sbt-tpolecat, not to allow.

sbt-tpolecat to automatically provide reasonable Scala compiler settings.

Start with settings strict compiler flags if you haven't already, for instance using sbt-tpolecat. This will help you remove the most obvious warts in your codebase.

However, after a while, I found that most of the things I needed were already covered by the compiler. And that Rob's (aka tpolecat) list of compiler options provided all the ones I needed for my style of coding. I Then learn that there was this sbt plugin that managed the list for me and also took care of changing the options according to the Scala version.

Sorry, have nothing useful to contribute (although I'd recommend you to set a restrictive set of scalac flags, for example from sbt-tpolecat, to let compiler help you), but just wanted to praise the Scala team and remind us of all those "Python 3 situation" rants we've saw 2 years ago and how silly they look now.