diff options
| author | Hans Bolinder <[email protected]> | 2018-05-24 12:21:21 +0200 |
|---|---|---|
| committer | Hans Bolinder <[email protected]> | 2018-05-25 09:46:47 +0200 |
| commit | 324fc38bc442460f871f3ae002dd853415ae9e51 (patch) | |
| tree | 26ea1179da346c7954a6064b05460c2eb7cbec0e /lib/dialyzer/test/specdiffs_SUITE_data/results/iodata | |
| parent | 4f91c8a34f4cc2c728a63e8d218566b3b3795b10 (diff) | |
| download | otp-324fc38bc442460f871f3ae002dd853415ae9e51.tar.gz otp-324fc38bc442460f871f3ae002dd853415ae9e51.tar.bz2 otp-324fc38bc442460f871f3ae002dd853415ae9e51.zip | |
dialyzer: Refine the test for overspecified functions
The -Woverspecs (-Wspecdiffs) option generates warnings in a few more
cases. The refinement is analogous to the test that -Wunderspecs
already does: it checks if the contract has nothing in common with
some element (see erl_types:t_elements/1) of the success typing.
Diffstat (limited to 'lib/dialyzer/test/specdiffs_SUITE_data/results/iodata')
| -rw-r--r-- | lib/dialyzer/test/specdiffs_SUITE_data/results/iodata | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/lib/dialyzer/test/specdiffs_SUITE_data/results/iodata b/lib/dialyzer/test/specdiffs_SUITE_data/results/iodata new file mode 100644 index 0000000000..3fb12fe000 --- /dev/null +++ b/lib/dialyzer/test/specdiffs_SUITE_data/results/iodata @@ -0,0 +1,3 @@ + +iodata.erl:7: The specification for iodata:encode/2 states that the function might also return binary() but the inferred return is nonempty_maybe_improper_list(<<_:8,_:_*8>> | nonempty_maybe_improper_list(<<_:8,_:_*8>> | nonempty_maybe_improper_list(any(),<<_:8,_:_*8>> | []) | byte(),<<_:8,_:_*8>> | []) | integer(),<<_:8,_:_*8>> | []) | integer() +iodata.erl:7: The success typing for iodata:encode/2 implies that the function might also return integer() but the specification return is binary() | maybe_improper_list(binary() | maybe_improper_list(any(),binary() | []) | byte(),binary() | []) |