Skip to content

Conversation

@vshakitskiy
Copy link
Contributor

@karlsson
Copy link

Since the reason type returned by Erlang for ssl:setopts is defines as just term() I guess this is the safest way to go. There is the type socket.SocketReason defined in glisten that seems to cover most reasons (einval for instance) but there is no guarantee it covers all there I think.
What you will lose now is how to see the fault that actually occurred.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants