anchor.diff:       race_conditions,
        behaviours,
        unmatched_returns,
  -     overspecs,
  -     underspecs,
  -     specdiffs].
  +     underspecs].
  
positive.code:             useful information. You can get around this by asking the
              dialyzer task to ignore certain applications. Do this in
              your build config with the following entry.  <break>  <break>
              {plt_ignore, [some_app1, some_app2]}.  <break>  <break>
              The downside, of course, is figuring out which apps actually
              have the problem. This task tries to help by printing out a
              list of applications that where under analysis when the blowup
  
negative.code:      filename:join([BuildDir, "deps.plt"])}.
  
  update_dep_plt(Config0, State0, DepPlt, AppList0) ->
      Ignores = Config0:match(dialyzer_ignore, []),
      AppList1 = [App ||
                     App = #app{name=Name} <- AppList0,
                     not lists:member(Name, Ignores)],
  