Today, setsockopt (at least) has a halt if an error occurred during its operations. Looking at the ZeroMQ header file in my build, it seems like the library uses different error codes than the normal ones. It would be good for us to:
[ ] define an Error subclass hierarchy for the ZMQ errors, and a factory method similar to how the SystemError hierarchy works to translate them from the C errno
The new functions I am adding in #12708 will use a ZMQError class, but there are still methods in this module that halt. Also, we still want to have some sort of hierarchy
Today, setsockopt (at least) has a halt if an error occurred during its operations. Looking at the ZeroMQ header file in my build, it seems like the library uses different error codes than the normal ones. It would be good for us to: