dialyzer unmatched return errors

[norton]

Using dialyzer's unmatched return analysis, the following dialyzer errors are reported for meck.

meck.erl:77: Expression produces a value of type ['ok'], but this value is unmatched
meck.erl:103: Expression produces a value of type ['ok'], but this value is unmatched
meck.erl:121: Expression produces a value of type ['ok'], but this value is unmatched
meck.erl:138: Expression produces a value of type ['ok'], but this value is unmatched
meck.erl:153: Expression produces a value of type ['ok'], but this value is unmatched
meck.erl:220: Expression produces a value of type ['ok'], but this value is unmatched
meck.erl:496: Expression produces a value of type 'ok' | {'error',atom()}, but this value is unmatched

[eproxus]

The fix would be to do this:

[ok = new(M) || M <- Mod], ok.

However, that still generates the same warning in dialyzer. I've emailed the mailing list reporting it as a false positive. Will look into it more once I get a reply.

[norton]

Ok. If you have time, please try the following ...

lists:foreach(fun(M) -> ok = new(M) end, Mod), ok.

[eproxus]

I already did and it removed the warnings. I'm skipping matching on ok though, because the functions only return ok anyways and will throw exceptions if something goes wrong.