diff options
| author | Hans Bolinder <[email protected]> | 2016-11-15 16:03:18 +0100 |
|---|---|---|
| committer | Hans Bolinder <[email protected]> | 2016-11-22 10:29:04 +0100 |
| commit | a202c2e0fa1f7810fb19c5a051369ce8b308ebc1 (patch) | |
| tree | 419bf3fc59eec3dd109d8da50a8f08b50d91c702 /AUTHORS | |
| parent | c79e32a66c366bbdf5025ad0ae7f7057a0ddb156 (diff) | |
| download | otp-a202c2e0fa1f7810fb19c5a051369ce8b308ebc1.tar.gz otp-a202c2e0fa1f7810fb19c5a051369ce8b308ebc1.tar.bz2 otp-a202c2e0fa1f7810fb19c5a051369ce8b308ebc1.zip | |
dialyzer: Improve a warning message
Messages like "Invalid type specification for function
para3:exp_adt/0. The success typing is () -> 3" now look like
"The specification for para3:exp_adt/0 has an opaque subtype
para3_adt:exp1(para3_adt:exp2()) which is violated by the success
typing () -> 3".
The old message did not give any clue as to what invalidated the
contract, namely the opaque subtype.
Diffstat (limited to 'AUTHORS')
0 files changed, 0 insertions, 0 deletions