Problem: zmq_disconnect documentation is confusing and breaks semantics
Solution: restore separate zmq_unbind documentation, adding a note that the implementation might be shared but the semantics are different and should not be mixed. This avoids tying the API to the implementation details which might change for some engines.
Showing
Please
register
or
sign in
to comment