Age | Commit message (Collapse) | Author | |
---|---|---|---|
2016-11-22 | dialyzer: Substitute 'opacity' for 'opaqueness' | Hans Bolinder | |
Suggested by Kostis. | |||
2014-06-17 | [dialyzer] Fix handling of literal records | Hans Bolinder | |
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. | |||
2014-01-21 | [dialyzer] Re-work the handling of opaque types | Hans Bolinder | |
It is now OK to inspect and modify the internals of opaque types within the scope of the module. The contracts are used for decorating types with opaqueness when it is harmless to do so. The opaqueness is propagated by the typesig module and also by the dataflow module. A lot of details have been fixed or updated. In particular the modules erl_types and erl_bif_types have been modified extensively. The version in vsn.mk has been updated to 2.7. The reason is a modification of #opaque{} in erl_types. Dialyzer seems to be about five percent slower than it used to be. |