gen_statem:start_monitor dialyzer warning
Tue Jan 26 10:45:27 CET 2021
I don't know about your specific question but...
On 26/01/2021 10:37, Raimo Niskanen wrote:
> We are still struggling with best practices for Dialyzer in an old large
> code base...
You have to run Dialyzer against tests. This is the best way to catch
the errors like the one in gen_statem:start_monitor because you need to
have calls to these functions for Dialyzer to do its work, and tests
tend to cover the entire public interface.
This does mean that some tests need to silence some Dialyzer warnings
when you do things wrong on purpose, though.
More information about the erlang-questions