otp.git/lib/dialyzer, branch OTP_R14B Mirror of Erlang/OTP repository. Prepare release 2010-09-13T15:58:05+00:00 Erlang/OTP otp@erlang.org 2010-09-13T15:58:05+00:00 17224a3d31d25ce6daa4de63b52b26bee9564bcd 






Remove warnings for clashes with new autoimported BIFs
2010-09-10T12:24:42+00:00

Patrik Nyblom
pan@erlang.org

2010-09-01T12:30:14+00:00

19a3f0c5bab37ba261abbca6c0253c1e3cb4d3ac












Update release notes
2010-06-11T12:15:26+00:00

Björn Gustavsson
bjorn@erlang.org

2010-06-11T10:20:20+00:00

08a112d189c8f47953eabcf2e05a0245dd6e6087












Various changes to dialyzer-related files for R14.
2010-06-08T14:47:40+00:00

Kostis Sagonas
kostis@cs.ntua.gr

2010-06-07T13:57:34+00:00

1a9e2dd394a81d01742593a5b42f9aa01bb5f276

Bumped version number and wrote RELEASE_NOTES.
Included all changes described in release notes.

Some spec-related changes to some files in lib/hipe/cerl.





Bumped version number and wrote RELEASE_NOTES.
Included all changes described in release notes.

Some spec-related changes to some files in lib/hipe/cerl.







Fix confusing dialyzer warnings for is_record/2 with illegal records
2010-06-07T09:02:31+00:00

Björn Gustavsson
bjorn@erlang.org

2010-06-07T09:02:31+00:00

707c6510597e5eb6e32b88412edd717e0e3c39ba

In commit 1858cb81391d2bce29b4b7620574ca60128cebf7, erl_expand_records
started to optimize is_record/2 in guards by replacing it with
pattern matching (if possible).

Unfortunately, dialyzer will no longer see the code before the
optimization, so any warnings produced in code such as:

  case ExprNotProducingRecord#rec{} of
         X when is_record(X, rec, N) -> ...

will refer to the optimized code and not the source code,
which is confusing for the user.

Introduce the no_is_record_optimization option for turning off
the optimization and use it in dialyzer.

Reported-by: Kostis Sagonas





In commit 1858cb81391d2bce29b4b7620574ca60128cebf7, erl_expand_records
started to optimize is_record/2 in guards by replacing it with
pattern matching (if possible).

Unfortunately, dialyzer will no longer see the code before the
optimization, so any warnings produced in code such as:

  case ExprNotProducingRecord#rec{} of
         X when is_record(X, rec, N) -> ...

will refer to the optimized code and not the source code,
which is confusing for the user.

Introduce the no_is_record_optimization option for turning off
the optimization and use it in dialyzer.

Reported-by: Kostis Sagonas







Minor fix in a print message
2010-06-03T12:34:27+00:00

Kostis Sagonas
kostis@cs.ntua.gr

2010-03-22T14:22:03+00:00

48599b841e7db3519825dd0d1464c38a53a1e9d5












Add handling of unknown types
2010-06-03T12:34:27+00:00

Maria Christakis
mchrista@greedy.softlab.ece.ntua.gr

2010-03-22T12:43:43+00:00

d775f62fd8f9f02679e0c5dd0ad3428dc22f7b93












Support -export_type() in dialyzer and erl_types
2010-06-03T12:34:26+00:00

Kostis Sagonas
kostis@cs.ntua.gr

2010-03-08T10:54:32+00:00

6452b57e6f6719febeb5d069ff3ffbdc23e5a4ad












Dialyzer docs: Fix minor typo
2010-04-09T12:49:28+00:00

Kostis Sagonas
kostis@cs.ntua.gr

2010-04-09T12:49:28+00:00

824d0fb5ae165a74350ad31f09f83ebc271b7c96












Fix small confusion/buglet in the handling of 'or'
2010-03-03T16:07:18+00:00

Kostis Sagonas
kostis@cs.ntua.gr

2010-03-03T16:07:18+00:00

4ca96c184819541fd9f67fc954d5dd9edb43e609