Jeremy Huffman

@kenny-evitt Yes exactly we don't control the analysis engine, just the integration and messaging, but we can still document some "tips" if there is no better place to start. The...

I'm fine with a change in contract and supporting both in Dialyxir.

Can you confirm if this is still an issue in rc.4 ? ` {:dialyxir, "~> 1.0.0-rc.4", only: [:dev], runtime: false} `

@jannamamer its fixed on master but hasn't been released on Hex yet.

See the discussion in https://github.com/jeremyjh/dialyxir/issues/224. I'm kind of leaning to your point of view now though; this message is probably a distraction in most cases. It is there so that...

I'm skeptical we can do anything helpful in `dialyxir`. This would need to be done in `dialyzer`. I mean yes maybe we could spew a bunch of xref at you,...

I was referring to using xref - I'm not sure we can even tell you who all the callees are from a given function. It looks like XRef only resolves...

I've used typer with erlang, but as far as I know it only accepts erlang source files as inputs. We're able to use dialyzer because it also accepts compiled BEAM...

It looks like its a new issue on Elixir 1.8. It works for me on 1.7.3 but I get the same error on 1.8. This code is a garbage fire,...

Umbrella projects share a build directory and a lock file, so they also share a PLT. Child projects reference the parents `mix.lock` file, so when that is changed a PLT...