See also https://bugs.erlang.org/browse/ERL-953.

* hasse/dialyzer/prettier_warnings/OTP-15135:
  dialyzer: Remove quotes around operators
  dialyzer: Add test cases with indentation
  dialyzer: Add an --no_indentation option
  dialyzer: Add parentheses around annotated union elements
  dialyzer: Fix dialyzer_dataflow:format_args_1()

A smallish selection of already existing tests, run with
the indentation option.

See also https://bugs.erlang.org/browse/ERL-845.

[Kostis:]

My suggestion is that the compiler refuses to compile modules that
contain specs for functions that are not from this module. I do not
remember when / why this `feature' was introduced, but thinking about
it I see a lot of (ugly) semantics issues with it. For example, should
one be allowed to declare in the foo module that lists:flatten/1 takes
an integer() as an argument and returns a binary()? Should one be
allowed to declare a spec in some module m1 for a function of m2 that
is not defined in m2?

There are all kinds of checks that will need to be added to dialyzer
to protect itself from these semantics issues. The compiler already
refuses to compile modules that contain specs for non-existing
functions of the module. Similarly, it should refuse to compile
modules that contain specs for functions of other modules - unless it
can somehow check that these functions are indeed defined, but it is
not how the compiler currently works.

In contracts, annotated elements of unions are printed with
parentheses around them. They are not parseable otherwise.

The mismatching argument positions are included.

Notice the comment in dialyzer_utils:

%% Copied from core_pp. The function cerl:binary_segments/2 should/could
%% be extended to handle literals, but then the cerl module cannot be
%% HiPE-compiled as of Erlang/OTP 22.0 (due to <<I:N>>).

When at it: simplify some common cases like "/binary-unit:8".

* maint:
  dialyzer: Fix maps as parameter of opaque types
  dialyzer: Fix key check of lists:key{search,member,find}()