Dialyzer v1.3.0 released
Jimmy Olgeni
olgeni@REDACTED
Thu Mar 24 13:09:27 CET 2005
On Thu, 24 Mar 2005, Tobias Lindahl wrote:
> Once again we are proud to release a new version of Dialyzer.
Maybe somebody should have a look into stdlib, I hope there are not that many improper lists :-)
{dict,counter_bkt,3}: Cons will produce a non-proper list since its 2nd arg is number()!
{dict,mk_seg,1}: The clause matching on the integer 4 will never match; argument is of type the integer 16
{dict,mk_seg,1}: The clause matching on the integer 8 will never match; argument is of type the integer 16
{dict,mk_seg,1}: The clause matching on the integer 32 will never match; argument is of type the integer 16
{digraph,new_edge_id,1}: Cons will produce a non-proper list since its 2nd arg is number()!
{digraph,new_vertex_id,1}: Cons will produce a non-proper list since its 2nd arg is number()!
{qlc_pt,element_calls,3}: Cons will produce a non-proper list since its 2nd arg is {'var',0,reference()}!
{qlc,abstract,2}: Call to '++'/2 will produce a non-proper list; 2nd arg is 'more'!
{qlc,append_loop,2}: Cons will produce a non-proper list since its 2nd arg is (() -> any())!
{qlc,cache,4}: Cons will produce a non-proper list since its 2nd arg is (() -> possibly_improper_list())!
{qlc,cache_recall,2}: Cons will produce a non-proper list since its 2nd arg is (() -> possibly_improper_list())!
{qlc,no_more,2}: Function has no local return
{qlc,size_bin,2}: Cons will produce a non-proper list since its 2nd arg is binary() | tuple()!
{qlc,no_dups,2}: Cons will produce a non-proper list since its 2nd arg is (() -> possibly_improper_list())!
{qlc,ucache3,7}: Cons will produce a non-proper list since its 2nd arg is (() -> possibly_improper_list())!
{qlc,ucache_recall,3}: Cons will produce a non-proper list since its 2nd arg is (() -> possibly_improper_list())!
{ets,qlc_next,2}: Call to '++'/2 will produce a non-proper list; 2nd arg is (() -> (() -> (() -> (() -> any()) | possibly_improper_list()) | possibly_improper_list()) | possibly_improper_list())!
{ets,qlc_prev,2}: Call to '++'/2 will produce a non-proper list; 2nd arg is (() -> (() -> (() -> (() -> any()) | possibly_improper_list()) | possibly_improper_list()) | possibly_improper_list())!
{ets,qlc_select,1}: Call to '++'/2 will produce a non-proper list; 2nd arg is (() -> (() -> (() -> (() -> any()) | possibly_improper_list()) | possibly_improper_list()) | possibly_improper_list())!
{erl_scan,more,7}: Call to '++'/2 will produce a non-proper list; 2nd arg is 'eof'!
{erl_scan,done,5}: Call to '++'/2 will produce a non-proper list; 2nd arg is 'eof'!
{erl_scan,tokens,3}: Call to '++'/2 will produce a non-proper list; 2nd arg is 'eof'!
{erl_tar,create_header,3}: Cons will produce a non-proper list since its 2nd arg is binary()!
{pg,master_loop,2}: Function has no local return
{slave,relay1,1}: Function has no local return
{pool,start,2}: Unsafe use of tuple as a fun in call to {lists,map,2}
{pool,stat_loop,2}: Function has no local return
{shell,eval_loop,3}: Function has no local return
{shell,restricted_eval_loop,4}: Function has no local return
--
jimmy
More information about the erlang-questions
mailing list