There is also GitHub - Premwoik/gradualizer-ex · GitHub
michallepicki
OvermindDL1
I was waiting on a few things to finish but never got around back to it, work got crazy in a few different ways than it was before. I specifically never published it because I didn’t consider it to be done enough for that and I didn’t want to potentially steal a good name for such a tool, so please, anyone fork it or remake it. 
This might indeed be the remake!
3
Fl4m3Ph03n1x
GitHub - Premwoik/gradualizer-ex · GitHub has been archived. I understand it is abandoned as well.
As far as I know, both Gradualizer ports to elixir have been put on ice. Until a new stable project comes along, there is no elixir candidate.
0
eksperimental
Fl4m3Ph03n1x
eksperimental
Errors are not that easy to read and I have the feeling that I get false positive errors which makes you waste lots of time tracking down and trying to fix something that is not broken.
1
erszcz
Thanks for the feedback! We’re trying to make Gradient as user-friendly as possible - there is significant effort put into making sure it integrates nicely with Elixir, but indeed, the software is still experimental.
Could you create a ticket with an error that you consider hard to read? Or given an example here? I’ll be happy to take it forward.
That’s the never ending story of type checkers / static analysis - how to make the checker detect real problems in code on one hand, yet still be flexible enough to allow for all quirks of the language and full expressiveness on the other. However, even more so in this case, we would be extremely happy if you could report false positives on the project’s GitHub page.
Any feedback is good feedback, so keep it coming 
I strongly believe it might only lead to making the tool better!
Getting back to main differences.
Gradualizer has a different approach than Dialyzer in reporting errors. Dialyzer advertises that “it’s never wrong”, which is true, but sometimes its feedback is a bit hard to use (the lovely “function … has no local return” and no direct hint on what to do with it). It’s also quite slow, though it’s not as much of a problem as it used to be a few years ago.
Gradualizer reports more kinds of errors and allows for some tricks known from other statically typed functional programming languages like exhaustiveness checking - see example screenshots of Gradualizer being used with the Erlang Language Server in this post. It’s also significantly faster, as it doesn’t require generating PLTs. Actually, thanks to its speed it’s very convenient as a background tool in the editor. However, in this experimental phase, it means some false positives might get reported.
To get a better feel of what’s possible with Gradualizer, that’s not possible with Dialyzer, you might want to watch my lightning talk about typechecking Elixir from ElixirConf EU 2021 or read about the typestate pattern in Erlang.
In the long run Gradient should offer everything Gradualizer does and maybe even a bit more thanks to some macro magic 
7
eksperimental
Hi,
I gave up on it on this project that had data structures of considerable length and it was taking a lot of time. As my library enters in a more stable status, I will give Gradualizer a second try and report the issues as it is my style.
Gradualizer detected some issues that Diaylzer didn’t so I am grateful for it.
I will try to use the tool as much as possible provided it is in an usable stage, if not put it not in my main flow of development but as an alternative one, and see what it can detect from time to time.
Thank you.
0
cjbottaro
This would be like a dream come true for me and several coworkers. We love Elixir, but often wish it had “opt-in strict static typing”… which this sounds exactly like “gradual typing”. Thank you for your work on this!
3
Rich_Morin
Can anyone tell me the status and prospects for type checking of message contents? I’ve only used Dialyzer in the context of a smallish Phoenix project and my impression is that it doesn’t even try to cover inter-process messages (but I could certainly be wrong – clues?).
While I’m at it, what about coverage of Nx-based data structures, etc? And a pony…
-r
1