Wartremover

Flexible Scala code linting tool (by wartremover)

Wartremover Alternatives

Similar projects and alternatives to Wartremover

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better Wartremover alternative or higher similarity.

Wartremover reviews and mentions

Posts with mentions or reviews of Wartremover. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-10-14.
  • New to Scala;
    8 projects | reddit.com/r/scala | 14 Oct 2022
    I was recently trying to move away from Scapegoat to Wartremover and I got bitten by this bug which is particularly prevalent in codebases using Typelevel libraries.
    8 projects | reddit.com/r/scala | 14 Oct 2022
    WartRemover to disable some of Scala’s more questionable features.
  • Which static analysis tool do you use for Scala?
    8 projects | reddit.com/r/scala | 12 Jan 2022
    There is also wartremover but you cannot run it separately from your compile command.
  • Newspeak and Domain Modeling
    4 projects | news.ycombinator.com | 29 Jun 2021
    or `NonUnitStatements` without explicit annotation.

    This effectively locks you into writing pure code (you can extend the linter to cover other things like not using `Future` or not using Java libs outside of `MonadError` from cats[4]). The linters operate on typed ASTs at compile time, and have plugins for the most popular scala build tools. Coupled with `-XFatalWarnings', you can guarantee that nothing unexpected happens unless you explicitly pop the escape hatch, for the most part.

    You can still bring in external libraries that haven't been compiled with these safties in place, so you aren't completely safe, but if you use ZIO[5]/Typelevel[6] libraries you can be reasonably assured of referentially transparent code in practice.

    There are three schools of thought, roughly, in the scala community towards the depth of using the type system and linters to provide guarantees and capabilities, currently:

    1) Don't attempt to do this, it makes the barrier to entry to high for Scala juniors. I don't understand this argument - you want to allow runtime footguns you could easily prevent at compile time because the verifiable techniques take time to learn? Why did you even choose to use a typesafe language and pay the compilation time penalty that comes with it?

    2) Abstract everything to the smallest possible dependency interface, including effects (code to an effect runtime, F[_] that implements the methods your code needs to run - if you handle errors, F implements MonadError, if you output do concurrent things, F implements Concurrent, etc.) and you extend the effect with your own services using tagless final or free.

    3) You still use effect wrappers, but you bind the whole project always to use a concrete effect type, avoiding event abstraction, thus making it easier to code, and limiting footguns to a very particular subset (mainly threadpool providers and unsafeRun or equivalent being called eagerly in the internals of applications).

    My opinion is that smallest interface with effect guarantees (#2) is best for very large, long maintenance window apps where thechoice of effect runtime might change(app), or is out of the devs' control (lib); and #3 is best for small apps.

    TL/DR; You can go a really, really long way to guaranteeing effects don't run in user code in scala. Not all the way like Haskell, but far enough that it's painful to code without conforming to referential transparency.

    1. https://github.com/scalacenter/scalafix

    2. https://github.com/scalaz/scalazzi

    3. http://www.wartremover.org/

    4. https://typelevel.org/cats/api/cats/MonadError.html

    5. https://zio.dev/

    6. https://typelevel.org/

  • A note from our sponsor - SonarQube
    www.sonarqube.org | 1 Dec 2022
    Your projects are multi-language. So is SonarQube analysis. Find Bugs, Vulnerabilities, Security Hotspots, and Code Smells so you can release quality code every time. Get started analyzing your projects today for free. Learn more →

Stats

Basic Wartremover repo stats
4
1,012
9.2
2 days ago
Truly a developer’s best friend
Scout APM is great for developers who want to find and fix performance issues in their applications. With Scout, we'll take care of the bugs so you can focus on building great things 🚀.
scoutapm.com