-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle Dialyzer warnings #81
Conversation
What about integers and other types? |
Fixes Dialyzer warning: The variable X__V can never match since previous clauses completely covered the type 'ok'
I believe integers should be covered by the second as in the test
|
So integers are returned as binary. Sad but true. |
The testcase parse_bulk_test is covering the same scenario as bulk_test, but was wrong (an underscore in ?_assertEqual)
A multibulk can contain a null value, like '$-1\r\n' which is an 'undefined' in the return_value().
The function will return {error, unknown_response} when an unknown type is found while parsing.
A gen_tcp:send / ssl:send can return errors like {'error','enotconn'} {'error', {'tls_alert', {'certificate_expired', _}}} which propagates to the user.
This makes sure we run dialyzer on testcode during development and in CI.
Run dialyzer on the test profile during
make dialyzer
, and in CI runs.This PR fixes all dialyzer warnings found in the
rebar3
test profile.