michallepicki / elixir-lang-dialyzer-runs Goto Github PK

Are these useful to keep track of them (can they help to detect real issues in code) or should I disable them? Example:

lib/module/parallel_checker.ex:199: Cons will produce an improper list since its 2nd argument is 
          binary()

Needs to support defining arbitrary pattern matching for the warning. Prerequisite for working towards specifying the pattern-matching based flexible filtering clauses inline in code.

Hi @michallepicki
I realized that as 'main' is developed, new changes are introduced in the stable release, and we are not covering those releases and the supported OTP versions for this release.

Right now the job always succeeds. After all non-issues are ignored, we can make it red whenever issues are found.

Allow to specify expected count per filter (default to at least one). Warn when count is off.

Many errors reported by dialyzer on the Elixir codebase are caused by:

• dead (or overly defensive) code
• deliberately accessing private Erlang APIs
• incomplete specs in Erlang code
• pattern matching on struct name for types marked as @opaque

We could maintain a list of known non-issues (with explainations) and filter them out from the dialyzer output. As a followup, exit status of the daily dialyzer check could be set accordingly (right now it is always green).