This ticket is about records in Erlang code, and when to check the
fields against the (optional) types given when defining records.

Dialyzer operates on the Erlang Core format, where there are no trace
of records. The fix implemented is a Real Hack:

Given the new option 'dialyzer' erl_expand_records marks the line
number of records in a way that is undone by v3_core, which in turn
inserts annotations that can be recognized by Dialyzer.

The fallback to latin-1 encoding would not work if the invalid
UTF-8 characters occurred in a skipped branch in an -ifdef/-ifndef.

* saa/add_default_value_for_maps_get/OTP-11951:
  stdlib: Fix indentation of maps doc
  Add docs and test for maps:get/3
  Add default value for maps:get

* fenollp/remove-erl_parse-legacy-map:
  Replace local mapl/2 (Erlang < 5.0) unique call by a LC

* nox/fix-eval-map-update/OTP-11922:
  Fix evaluation of map updates in the debugger and erl_eval

* bjorn/stdlib/erl_tar/OTP-11854:
  Correct typo in type specification
  Fix typo in erl_tar docs
  Update information about compatibility
  Correct end of tape marker
  Support path names with characters outside the US ASCII range

The POSIX standard for tar says that there must be at least
two 512-bytes zero blocks at the end of the tar archive file.

Our implementation would only emit a single 512-byte zero block if the
size of the last file was in the range 18*512 through 19*512-1 (modulo
20*512). GNU tar would correctly unpack such tar archive file, but
would emit a warning:

   tar: A lone zero block at 20

* bjorn/stdlib/file_lib-wildcard/OTP-11850:
  filelib:wildcard() should show broken symlinks