Hey jxub, nice to meet you as well and I hope you’re progressing well
Also thanks to @christhekeele, you’ve really nailed it

It’s been pretty much 1 month I’ve been working on mix-dialyzer, and I have some nice news: now mix_dialyzer is in an apha stage, where you can use it to analyse your projects based on a configuration file, get informations about your project status and manage the artefacts generated.

Inside, it already caches some common things, although I still have to implement a proper caching system.

I’ve also published a doc page, explaining every implemented functionality in detail, you can find it here: mix-dialyzer/doc at master · gabrielgatu/mix-dialyzer · GitHub

Let me know if you have any question or suggestion to make things better

Hi @gabrielgatu , nice to meet a fellow GSoC’er . It seems like you’ve got quite an interesting challenge and the README looks really good!

Let me also use the thread to introduce myself I’m Jakub and I’ve just started working on BarrelEx, an Elixir API for BarrelDB, an distributed document-oriented database written in Erlang, and I’m mentored by Benoît Chesneau, its creator.

I’ve already covered around 50% of the API, and still need to add more test coverage as well as through documentation. The code is hosted on Gitlab due to its superior CI story but you can also see the Github mirror here https://github.com/jxub/barrel_ex

My understanding is the project means to better integrate dialyzer’s success typing with Elixir and mix, not re-implement it.

In particular, I am pretty sure they are trying to add builtin mix commands capable of faster, incremental dialyzer runs; and improve the error messages it gives from its current cryptic literal success-typing messages to the more friendly and instructive ones we are used to in Elixir, with examples/suggestions around common mistakes.