Confusing error from ssl:connect/3 when Host is a binary

[rlipscombe]

Describe the bug

The error reported by ssl:connect/3 when Host is a binary (or otherwise not a string?) is confusing/misleading:

1> application:ensure_all_started(ssl).
{ok,[crypto,asn1,public_key,ssl]}
2> ssl:connect(<<"localhost">>, 55156, [{verify, verify_none}]).
{error,{options,{socket_options,[{packet_size,0},
                                 {packet,0},
                                 {header,0},
                                 {active,false},
                                 {mode,binary}]}}}

Expected behavior

A badarg error/exception or similar. Not something that complains about socket_options, anyway.

Affected versions

OTP-26.x, OTP-27.x, OTP-28.0.1

[IngelaAndin]

Looks like the assumption was that badarg would come form the options list and not from the host argument. This should improve things. Further improvements would require gen_tcp error handling to be updated. That might be a good thing but another issue.