otp.git/lib/stdlib/src, branch OTP-21.1.4

stdlib: Allow lists with binaries in the Format argument

2018-09-17T11:19:30+00:00

As a consequence of some refactoring (OTP-14983, option
'chars_limit'), the Format argument of io_lib:format() no longer
accepts binaries in lists in Erlang/OTP 21.0.

Note that if Format is not of type io:format(), control sequences in
Format are ignored. This can result in unpredictable behaviour if, for
example, the output of io_lib:format() is used as Format: if the
output happens to be a string(), then control sequences are
interpreted, otherwise not.

A check that Format is of type io:format() will likely be introduced
in Erlang/OTP 22.0. That will probably mean work for some users, but
considering how unpredictable io_lib:format() is, we should try to fix
that.

[proc_lib] Improve crash reports for single line logging

2018-09-12T12:58:02+00:00

[logger] Remove encoding option from logger_formatter

2018-09-12T12:58:02+00:00

The encoding option was introduced in commit
270d909696a753af022df72a404c73f2895b4a02, to allow report callbacks to
format according to a given encoding. There was, however, no
connection between this encoding option, and the encoding of the
device to which the logger handler was writing.

Since a formatter is defined to return unicode:chardata(), and in
order to avoid mismatch with the encoding of the device, the encoding
option is now removed from the formatter. The handler itself must make
sure that it does not write illegal data to its device.

Fix type spec of ms_transform:parse_trans/2

2018-08-30T23:29:42+00:00

It can also return errors and warnings.

Merge pull request #1940 from uabboli/hb/stdlib/fix_dets_file_name/OTP-15253/ERL-555

2018-08-28T06:32:08+00:00

stdlib: Let dets:open_file() crash when given raw file name

stdlib: Fix specs of filename:basedir/2,2

2018-08-22T07:37:14+00:00

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

stdlib: Let dets:open_file() crash when given raw file name

2018-08-21T06:20:53+00:00

See also ERL-55 and OTP-13229.

stdlib: Correct contracts in module io_lib_format

2018-08-20T12:05:56+00:00

stdlib: Improve error handling in module io_lib

2018-08-20T12:05:56+00:00

Correct error behavior of is_map_key/2 in guards

2018-08-13T07:26:36+00:00

Consider the following functions:

    foo() -> bar(not_a_map).

    bar(M) when not is_map_key(a, M) -> ok;
    bar(_) -> error.

What will `foo/0` return? It depends. If the module is compiled
with the default compiler options, the return value will be
`ok`. If the module is compiled with the `inline` option,
the return value will be `error`.

The correct value is `error`, because the call to `is_map_key/2`
when the second argument is not a map should fail the entire
guard. That is the way other failing guards BIFs are handled.
For example:

    foo() -> bar(not_a_tuple).

    bar(T) when not element(1, T) -> ok;
    bar(_) -> error.

`foo/0` always returns `error` (whether the code is inlined
or not).

This bug can be fixed by changing the classification of `is_map_key/2`
in the `erl_internal` module. It is now classified as a type test,
which is incorrect because type tests should not fail. Reclassifying
it as a plain guard BIF corrects the bug.

This correction also fixes the internal consistency check
failure which was reported in:

https://bugs.erlang.org/browse/ERL-699