4 ms·
> Dialyzer via Dialyxir is imperfect Imperfect is putting it lightly. I loathe it. Aside from useless errors ("here's what the success typing looks like! Ignor
by pavel_lishin 7y ago
> Dialyzer via Dialyxir is imperfect
Imperfect is putting it lightly. I loathe it. Aside from useless errors ("here's what the success typing looks like! Ignore the any()s, and fix it! But I won't tell you what's _wrong_!"), it doesn't run against tests (which bit my ass in production last month due to some return values being ignored, and only actually matched in tests.)
> especially with the error message improvements available via my Erlex library
My interest is piqued. Does it help unfuck Dialyzer error messages?
- verttii 7y agoI agree, Dialyzer is just... horrible. It' hard to find anything good to say about it, unfortunately. Not that it's a trivial problem to solve, I get that.
- PopeDotNinja 7y agoAs someone who quite likes dialyzer, it is most certainly not optimized for user experience :P
- _asummers 7y agoThere is a `mix dialyzer.explain no_return` and such, which gives you at least an intuition about what the errors are looking for. Re: my library, the Erlang error messages are just wholly inappropriate so it lexes, parses and pretty prints them to give a much better user experience, due to an upstream decision to not offer the errors in AST form.