Gradualyzer vs Dialyzer - main differences?

Dialyzer was build on the idea of success typing. This makes so that dialyzer can work even without user input, just based on code itself. It also tries to not report false positives quite heavily. But it comes with the downside of not detecting many of the error cases other static typing systems can detect. (The link below even argues that dialyzer is not a type system)

Gradualizer is a completely different approach. Afaik it doesn’t do type inference, so unless you manually provide typespecs it does nothing. But for the places you do provide them, it’ll statically check for errors even beyond what dialyzer would be able to detect or would acknowledge. The other big part between the lines is that you can gradually add type safety to your systems. It’ll work with as much typespecs as the code does provide.

For more details see this one:
https://github.com/josefs/Gradualizer/blob/master/talks/talk.md#comparison-with-dialyzer

Essentially both tools try to detect errors, but do that in quite different ways with therefore quite different tradeoffs.

Have you used both tools in concert in a project? I’m curious since I’m considering it.

I have not. I’ve just seen the talk about gradualizer.

Are there any tutorials/articles how to use gradualizer with Elixir?

@OvermindDL1 created Gradualixir ( GitHub - OvermindDL1/gradualixir: Gradualizer Mix Wrapper · GitHub ). Right now I think it is the best shot at using Gradualizer with Elixir. If you have any questions you can probably ask him.

I think gradualixir is in a slightly broken state due to recent changes in gradualizer (again), PR’s to fix welcome, and I probably need to track specific commits instead of master until gradualizer publishes it’s first release.

But when it works you just run mix gradualizer to scan your whole project or mix gradualizer files.beam morefiles.beam path/**/to/files/*.beam, recommend to do individual files for now to work on errors at a time to fix things (when it’s in a working state). Gradualixir itself passes gradualizer (and dialyzer) with flying colors though.

I heard the Running in Production podcast where you talked about Gradualizer and other stuff. Very nice episode You seem to follow the development of Gradualizer closely, do you know when it will stable enough to use and what the current state is?

Seems to be progressing fairly quickly, dev seems to have slowed lately as most of it is pretty well done now, mostly just needs more typespecs fixing broken typespecs. Other than that it’s usable now for most things, just more typespecs, lol.

The most recent commit to Gradualixir was almost two years ago. Can someone give me an idea of its current status and prospects? Is anyone using it as a production tool?

-r

(crickets…)