Remove the "coding: utf-8" comment from all Erlang source files
Convert XML files to UTF-8, where needed
Convert XML files to UTF-8
Merge branch 'maint'
Merge branch 'maint'
Merge branch 'maint'
Merge tag 'OTP_R16B01'

The R16B01 release

Conflicts:
	lib/sasl/vsn.mk
Merge branch 'maint'
Merge branch 'maint'
Merge branch 'maint'
Merge branch 'maint'

* maint:
  Change encoding of troublesome notes.xml files to utf-8
  Convert some notes.xml files from latin-1 to utf-8
Merge tag 'OTP_R16B02'

The R16B02 release

Conflicts:
	lib/sasl/vsn.mk
Merge branch 'maint'
Merge branch 'maint'
Merge branch 'maint'
Merge branch 'maint'
erts: Add erlang wrappers to binary_to_term

to not expose the trapping BIF in the stacktrace
when it throws badarg.
Merge branch 'maint'
Merge tag 'OTP_R16B03'

The R16B03 release

Conflicts:
	lib/sasl/vsn.mk
EEP 37: Funs with names

This adds optional names to fun expressions. A named fun expression
is parsed as a tuple `{named_fun,Loc,Name,Clauses}` in erl_parse.

If a fun expression has a name, it must be present and be the same in
every of its clauses. The function name shadows the environment of the
expression shadowing the environment and it is shadowed by the
environment of the clauses' arguments. An unused function name triggers
a warning unless it is prefixed by _, just as every variable.
Variable _ is allowed as a function name.

It is not an error to put a named function in a record field default
value.

When transforming to Core Erlang, the named fun Fun is changed into
the following expression:

    letrec 'Fun'/Arity =
               fun (Args) ->
                       let <Fun> = 'Fun'/Arity
                       in Case
    in 'Fun'/Arity

where Args is the list of arguments of 'Fun'/Arity and Case the
Core Erlang expression corresponding to the clauses of Fun.

This transformation allows us to entirely skip any k_var to k_local
transformation in the fun's clauses bodies.