Gradualizer VS gradient

Gradualizer is a typechecker for Erlang. It's a bidirectional typechecker, which means it uses non-local type inference, i.e. a blend of typechecking with type inference. It aims to follow the principles of gradual typing, so that it's possible to add type annotations only to parts of your code, instead of the entire code base, and it's going to work with that. One of the eqwalizer authors, Ilya Klyuchnikov, contributed to Gradualizer in the past.

If you're looking for compile-time (or actually check-time) feedback you might be interested in Gradient, a gradual type checker for Elixir and a frontend to Gradualizer. These tools, while experimental, allow for applying "making illegal states unrepresentable" principle thanks to exhaustiveness checking. In general, they are more akin to the ML-style type checking than Dialyzer is.

I'm hoping that https://github.com/josefs/Gradualizer and its Elixir counterpart get us closer to what "I" want. I find dialyzer often inscrutable compared to something like OCaml's or Haskell's type errors.

I do still use it and typespecs, because it's better than no checking.

There's Gradualyzer with support for Gradual Typing on the way.

There's an effort currently being led by Facebook to create gradual type system for Erlang call Gradualizer, which should also make its way over to Elixir.

https://github.com/josefs/Gradualizer

If you're into trying out static typing in Elixir, please check out https://github.com/esl/gradient. It's still experimental, but already functional. We're happy to get any feedback or, better yet, contributions.

If you're looking for compile-time (or actually check-time) feedback you might be interested in Gradient, a gradual type checker for Elixir and a frontend to Gradualizer. These tools, while experimental, allow for applying "making illegal states unrepresentable" principle thanks to exhaustiveness checking. In general, they are more akin to the ML-style type checking than Dialyzer is.